[aws-for-fluent-bit] How to get this chart to deploy the same configmap as the AWS documentation
- Dominant language
- Mustache
- Stars
- 1.3k
- Forks
- 1.1k
- Avg merge
- 22m
- Merged PRs (30d)
- 5
Description
**Is your feature request related to a problem?**
Hello all. The feature request/guidance that i'm looking for is related to discrepancies between the configmap within the helm chart that is deployed for 'aws-for-fluent-bit' verse what the official [AWS documentation](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/Container-Insights-setup-logs-FluentBit.html) includes. Following the manual process via the docs, we should have additional log streams, like '/dataplane', '/host', and '/application'. However, when deploying via the chart, we have more limited streams that are created. The biggest issue i'm seeing is that we're not collecting kubelet logs via the helm method by default, and I'm struggling to find a good example that allows us to do that through helm.
**Is your feature request related to a specific Helm chart, if yes mention name of the chart?**
aws-for-fluent-bit
**Describe the solution you'd like**
I'd like either an example added, or default values incorporated into the configmap that will allow us to retrieve kubelet logs
Any help would be appreciated. Thank you!
Contributor guide
Research direction
Start with the aws-for-fluent-bit Helm chart's ConfigMap and values, then compare its generated configuration with the AWS Container Insights documentation linked in the issue. Confirm how the chart can collect kubelet logs and create the /dataplane, /host, and /application streams; done means a documented example or default values that deploy this configuration through Helm.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, helm
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100