Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EKS: Helm Chart for Fluient-Bit could use Retry-Limit field #1616

Open
stevcos opened this issue Jan 3, 2022 · 0 comments
Open

EKS: Helm Chart for Fluient-Bit could use Retry-Limit field #1616

stevcos opened this issue Jan 3, 2022 · 0 comments
Labels
Proposed Community submitted issue

Comments

@stevcos
Copy link

stevcos commented Jan 3, 2022

Community Note

  • Please vote on this issue by adding a 👍 reaction 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.

@stevcos stevcos added the Proposed Community submitted issue label Jan 3, 2022
@stevcos stevcos changed the title [service] [request]: describe request here EKS: Helm Chart for Fluient-Bit could use Retry-Limit field Jan 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Proposed Community submitted issue
Projects
None yet
Development

No branches or pull requests

1 participant