Upgrade fluentbit chart with image and new set of config values
- 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?**
There have been significants updates to fluentbit, specially cloudwatch plugin in recent times.
In recent times, they have released a new plugin `cloudwatch_logs` which brings in tons of feature like ability to define log_group_template which allows to create cloudwatch log groups dynamically.
It new plugin `cloudwatch_logs` should replace the [aws/amazon-cloudwatch-logs-for-fluent-bit](https://github.com/aws/amazon-cloudwatch-logs-for-fluent-bit) Golang Fluent Bit plugin released last year as recommended by repository readme. The Golang plugin was named `cloudwatch`; this new high performance CloudWatch plugin is called `cloudwatch_logs` to prevent conflicts/confusion.
I think this problem surfaces an issue where customers should be able to override config maps like one can override settings like container image while it can continue to have current implementation for abstractions. This way helm-charts can stay agile and updated.
**Is your feature request related to a specific Helm chart, if yes mention name of the chart?**
fluent-bit
**Describe the solution you'd like**
Ability to override config map for fluent bit as a whole
**Describe alternatives you've considered**
Continually update new settings and plugin with new releases and implement similar one for `cloudwatch_logs`
Contributor guide
Research direction
Start with the fluent-bit Helm chart's existing values, image settings, and ConfigMap template, then trace how current Fluent Bit configuration is assembled. Compare the requested cloudwatch_logs support and whole-ConfigMap override with the chart's current abstractions. Done means the chart can use the updated image and lets users override the complete ConfigMap while retaining the existing configuration path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100