aws / aws/containers-roadmap

[EKS]: amazon-cloudwatch-observability addon having issue when passing fluentBit config using configuration_values

Open
#2,471 4 comments 0 reactions 0 assignees View on GitHub
EKS EKS Add-Ons
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

I am creating EKS CloudWatch Observability addon using Terraform with this config. All custom configurations are available in configs directory.

![image](https://github.com/user-attachments/assets/4851790d-ab10-4268-9a79-c837e2ef1e1a)

When deploying it, it goes timed-out after 20 minutes

While exploring the logs of fluentbit pods, it shows file is already available and contains error. If I delete default config and deploy same configurations using terraform_data source, it deploys and works perfectly fine.

![image](https://github.com/user-attachments/assets/7bffefb7-d71c-4a88-9d6e-f5de22d3987a)

Contributor guide

Open the contributing guide

Research direction

Review the custom configurations in the configs directory and the Terraform configuration that passes configuration_values to the Amazon CloudWatch Observability addon. Start by reproducing the deployment timeout and inspect the fluentbit pod logs, including the reported file-already-available error. Done means the addon deploys successfully with the custom configuration instead of timing out.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes, terraform
Domain
cloud, devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.