IBM Cloud - Structured Ideas

Welcome to the idea portal for structured ideas (i.e. product feature requests) - A more integrated and automated feedback system to connect your product improvement ideas with IBM product and engineering teams.  Happy submitting!

 

NOTE: All IBM employees must enter Ideas through this Ideas Portal.

Kubernetes worker node upgrade should respect PodDisruptionBudget

We are using Kubernetes PodDisruptionBudget to prevent voluntary disruptions of services. This should include the drain of worker nodes during worker node upgrade. While a manual kubectl drain fails in case of insufficient running replicas, IBM Cloud worker node upgrade ignores the PodDisruptionBudget and proceeds with the shutdown of the worker node.

Knowing that, I have to check every service regarding a defined PDB and whether the upgrade will cause a disruption in sense of PDB or not. The other option is to drain every node manually to see if it complies with the PDB.

So please make the automations for the worker node upgrade aware of the actual work load and respect the PDB and not only the ConfigMap ibm-cluster-update-configuration with the unavailability rules on worker node level.

Proposed solution:
provide a second workload aware upgrade option, so the user can choose (and can still use the existing forced upgrade option)

  1. start draining the worker nodes as long as the worker node unavailability rules allow
  2. if a drain fails, cancel the upgrade of the worker node and uncordon the worker node
  3. proceed with remaining worker nodes as long as the worker node unavailability rules allow
  4. inform user about failed drains and possible reasons (PDB, gracefully termination period) and solutions (just retry, manual drain, move pods, forced upgrade option)
  • Guest
  • Jan 8 2020
  • Future Backlog
  • Attach files

NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "anonymous@euprivacy.out" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions