Skip to content

Conversation

@mikkeloscar
Copy link
Contributor

Don't treat kubenurse as a critical daemonset that must be ready before a node is ready. This way if kubenurse it failing for whatever reason, nodes will still be ready for user workloads.

depends on #8576

@mikkeloscar mikkeloscar added the minor Minor changes, e.g. low risk config updates, changes that do not introduce a new API call. label Dec 5, 2024
@mikkeloscar
Copy link
Contributor Author

👍

Base automatically changed from container-registry.zalando.net/teapot/kube-node-ready-controller to dev December 5, 2024 13:17
@zaklawrencea
Copy link
Member

👍

@zaklawrencea zaklawrencea merged commit fd6eb3f into dev Dec 5, 2024
10 checks passed
@zaklawrencea zaklawrencea deleted the exclude-kubenurse branch December 5, 2024 13:23
This was referenced Dec 5, 2024
@k8s-on-aws-manager-app k8s-on-aws-manager-app bot mentioned this pull request Dec 6, 2024
@k8s-on-aws-manager-app k8s-on-aws-manager-app bot mentioned this pull request Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merged/alpha merged/beta merged/eks merged/stable minor Minor changes, e.g. low risk config updates, changes that do not introduce a new API call.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants