EKS: Helm Chart for Fluient-Bit could use Retry-Limit field
- Dominant language
- Shell
- Stars
- 5.4k
- Forks
- 334
- PR merge metrics
- No merged PRs in 30d
Description
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
**Tell us about your request**
The ability for the helm chart for aws-for-fluent-bit (link: https://github.com/aws/eks-charts/tree/master/stable/aws-for-fluent-bit ) to have the field for the scheduler's Retry limit to be changed.
**Which service(s) is this request for?**
EKS
**Tell us about the problem you're trying to solve.**
The helm chart does not allow for the field to be changed at creation, so its assumed to be the default of 1. Would like the ability to set it to be higher or unlimited in the chart itself rather than manually later.
Contributor guide
Research direction
Start with the stable/aws-for-fluent-bit Helm chart linked in the issue and inspect how its configuration is rendered. Verify the chart with Helm using a custom scheduler retry limit; the work is done when the limit can be set during creation, including an unlimited option if supported by the chart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, helm, kubernetes
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100