This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
You shouldn't need to do much about it. After you cordoned the node
nothing new will be scheduled to this node. To remove it you can delete
/ reschedule all pods that are running on it; once gone it should be
deleted by autopilot automatically.
We're also running similar weird issues. For the K8S init container it
somehow sums the storage it requested it self (1GiB) with what we
requested for the main container (10GiB), and now GKE-warden rejects the
image because 11 > 10G. We didn't see th...
