Add Retry_Limit property to the aws-for-fluent-bit eks chart
- Dominant language
- Mustache
- Stars
- 1.3k
- Forks
- 1.1k
- Avg merge
- 22m
- Merged PRs (30d)
- 5
Description
Today, in order to use the aws-for-fluent-bit EKS Helm chart to configure the Kinesis plugin, we have had to hard-code the Retry_Limit property after [this line](https://github.com/aws/eks-charts/blob/master/stable/aws-for-fluent-bit/templates/configmap.yaml#L152) with the value ```Retry_Limit no_limits``` in order to ensure that fluent bit perpetually continues to retry writing messages to the Kinesis stream.
Please add this entry and the corresponding value to [the aws-for-fluent-bit chart](https://github.com/aws/eks-charts/tree/master/stable/aws-for-fluent-bit).
After inquiring about this with AWS support, the support tech opened [this issue](https://github.com/aws/containers-roadmap/issues/1616) for your cross reference as well.
Contributor guide
Research direction
Start with stable/aws-for-fluent-bit/templates/configmap.yaml at the linked line and inspect the surrounding aws-for-fluent-bit chart configuration. Add the Retry_Limit entry and its corresponding value, then verify that the chart contains the requested Kinesis retry setting.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100