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
It could be nice to be able to configure additional conditions which will trigger fencing.
The motivation to have it is that if one uses Kubernetes Node-Problem-Detector, there could be more conditions which are configured by an administrator.
These conditions may not cause a Node to have Ready=false but may still require fencing (node reboot) to restore normal operation.
P.S. I may try to make necessary changes, if this is considered to be a necessary feature.
The text was updated successfully, but these errors were encountered:
At the moment, the fencing controller checks only
NodeReady
condition ( https://github.com/kvaps/kube-fencing/blob/master/pkg/controller/node/node_controller.go#L92 ).It could be nice to be able to configure additional conditions which will trigger fencing.
The motivation to have it is that if one uses Kubernetes Node-Problem-Detector, there could be more conditions which are configured by an administrator.
These conditions may not cause a Node to have
Ready=false
but may still require fencing (node reboot) to restore normal operation.P.S. I may try to make necessary changes, if this is considered to be a necessary feature.
The text was updated successfully, but these errors were encountered: