You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should provide a MachineHealthCheck definition for both the control-plane and the machines (excluding machine pools). We will set sane defaults for now.
In working with MHC I found that setting nodeStartupTimeout: 10m helps as an instance can take a while to come up. `10m1 might be too long, but we should set something higher than whatever the default is.
What would you like to be added:
We should add some basic MHC to our templates so that unhealthy nodes can be handled
MHC docs: https://cluster-api.sigs.k8s.io/tasks/automated-machine-management/healthchecking.html
We should provide a
MachineHealthCheck
definition for both the control-plane and the machines (excluding machine pools). We will set sane defaults for now.For more details on this see the proposal: https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/proposals/20191030-machine-health-checking.md and the feature PR: kubernetes-sigs/cluster-api#3830
Why is this needed:
If a node fails to launch or is terminated for some reason we want CAPI to bring up a new node.
The text was updated successfully, but these errors were encountered: