Using vanilla fluent-bit image with aws-for-fluent-bit helm chart
- Dominant language
- Mustache
- Stars
- 1.3k
- Forks
- 1.1k
- Avg merge
- 22m
- Merged PRs (30d)
- 5
Description
Hey All,
Are there any known issues with using the vanilla fluent-bit image with the aws-for-fluent-bit helm chart? Should things largely "just work" or are there known integration issues or any kind? Anything to be made aware of? I know there is an open ISSUE with aws-for-fluent-bit to support fluentbit 2.x but not sure that is getting any traction one way or another so we wanted to give things a go with vanilla fluent-bit but keep the same helm chart so as to minimize the amount of changes we need to make on our end.
CC @PettitWesley
Thanks,
Chris
Contributor guide
Research direction
The issue names no files, tests, or entry points. Start by reviewing the aws-for-fluent-bit Helm chart’s image and configuration values, then compare them with the vanilla Fluent Bit image; done would be documented guidance on compatibility and any required changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, helm, kubernetes
- Domain
- cloud, devops
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100