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.

Sign up for GitHub

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

Jump to bottom

[Doc] Use startup taint for better cluster-autoscaler behaviour #160

Open
b4nst opened this issue Dec 13, 2024 · 0 comments
Open

[Doc] Use startup taint for better cluster-autoscaler behaviour #160

b4nst opened this issue Dec 13, 2024 · 0 comments

Comments

@b4nst
Copy link

b4nst commented Dec 13, 2024

I think it would be beneficial for user to replace the taint example (kubeip.com/not-ready) by a startup taint (startup-taint.cluster-autoscaler.kubernetes.io/kubeip-not-ready or equivalent). This would avoid a chicken and egg scheduling issue, as startup taint are ignored by cluster-autoscaler.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@b4nst