We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Which component are you using?:
cluster-autoscaler
What version of the component are you using?:
Component version: All
What k8s version are you using (kubectl version)?:
kubectl version
Not relevant
What environment is this in?:
What did you expect to happen?:
To have all the Autoscaler parameters documented.
What happened instead?:
At least 2 parameters were missing.
How to reproduce it (as minimally and precisely as possible):
Search for node-deletion-delay-timeout or node-deletion-batcher-interval in the FAQ page.
node-deletion-delay-timeout
node-deletion-batcher-interval
Anything else we need to know?:
Nope
The text was updated successfully, but these errors were encountered:
/area cluster-autoscaler
Sorry, something went wrong.
Hi @pierluigilenoci, there is already PR #7014 opened for adding all the parameters/flags in FAQ.md. PTAL!
@Shubham82 Well, let's merge it then. 🚀
Yeah, waiting for other members' opinions on Log flags, I hope it will mere soon.
@Shubham82 any feedback?
Successfully merging a pull request may close this issue.
Which component are you using?:
cluster-autoscaler
What version of the component are you using?:
Component version: All
What k8s version are you using (
kubectl version
)?:Not relevant
What environment is this in?:
Not relevant
What did you expect to happen?:
To have all the Autoscaler parameters documented.
What happened instead?:
At least 2 parameters were missing.
How to reproduce it (as minimally and precisely as possible):
Search for
node-deletion-delay-timeout
ornode-deletion-batcher-interval
in the FAQ page.Anything else we need to know?:
Nope
The text was updated successfully, but these errors were encountered: