IBM Cloud - Structured Ideas

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and vote them if they matter to you

  1. Post an idea

  2. Vote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

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 consideration
Idea priority High

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.