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 doesn't look to me as if the code uses any graceful draining of the Kubernetes nodes at present?
It would be good to add this into the node termination procedure so that pods are moved off of the instance before termination on AWS.
I'm thinking about cases when terminating a node would disrupt a PDB, if there's no budget then ideally you wouldn't terminate the node until there is budget
The text was updated successfully, but these errors were encountered:
We could add this as a flag --drain-nodes or something. You could get into a weird state where it's draining the node it's on so you would have to work around that.
It was intentional to have it aggressively terminate nodes as it will expose single points of failure and kind of simulate a node breaking.
It doesn't look to me as if the code uses any graceful draining of the Kubernetes nodes at present?
It would be good to add this into the node termination procedure so that pods are moved off of the instance before termination on AWS.
I'm thinking about cases when terminating a node would disrupt a PDB, if there's no budget then ideally you wouldn't terminate the node until there is budget
The text was updated successfully, but these errors were encountered: