[EKS] [request]: Ability to change kube controller manager parameters such as '--terminated-pod-gc-threshold'

[hshabbar]

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 What do you want us to build?

Ability to set values for kube controller manager parameters such as --terminated-pod-gc-threshold

Which service(s) is this request for? EKS

[sidewinder12s]

@mikestef9 Is the value that EKS uses for this flag documented anywhere?

[dmegyesi]

@mikestef9 Is the value that EKS uses for this flag documented anywhere?

You can check it in Cloudwatch when you enable the control plane logging. In my EKS 1.21 cluster it's: --terminated-pod-gc-threshold="12500"

[sidewinder12s]

That's long ago deleted, though I'll take that as its set to the default.

[mtcode]

Another flag that should be configurable is --horizontal-pod-autoscaler-tolerance. The default value is 0.1, or 10%, but there are use cases to make the value smaller (more sensitive, more responsive) or larger.

[raravena80]

+1 we need this feature

[ozcb]

+1

[adamdougal]

Just to add to the list of parameters that we'd like configurable. --concurrent-horizontal-pod-autoscaler-syncs which is new in K8s 1.26.

[Aym3nTN]

Is there like any reason to not allow overriding this --terminated-pod-gc-threshold default value? it's really a pain to have to clean up those terminated pods manually or having a cronjob to do it...

[parvez99]

Any plans of having this feature rolled out anytime soon ? This would be very helpful.

[MedAzizTousli]

+1 for this very important feature.

[qxmips]

+1