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

No automatic node replacement when change nodepool properties like taints #281

Open
g-iannelli opened this issue Feb 21, 2023 · 0 comments
Open

No automatic node replacement when change nodepool properties like taints #281

g-iannelli opened this issue Feb 21, 2023 · 0 comments
Labels
bug Something isn't working furyctl-ng help wanted Extra attention is needed size/XXL

Comments

@g-iannelli
Copy link
Contributor

g-iannelli commented Feb 21, 2023 •
edited
Loading

If you remove a taint or change instance_type from a nodepool, the nodes are not automatically replaced, which means that old nodes still exist with the previous taints/instance_type and the desired state does not match the real one
@g-iannelli g-iannelli added bug Something isn't working furyctl-ng labels Feb 21, 2023
@omissis omissis added help wanted Extra attention is needed size/XXL labels Feb 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working furyctl-ng help wanted Extra attention is needed size/XXL
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@omissis @g-iannelli