Skip to Main Content
IBM Cloud - Structured Ideas

This portal is to open public enhancement requests against IBM Cloud and its products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (

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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

IBM Cloud Support Center ( – Use this site for any IBM Cloud defect or support need.

Stack Overflow ( – Use this site for IBM Cloud technical Q&A using the tag "ibm-cloud". - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Categories Kubernetes Service
Created by Guest
Created on Jul 26, 2023

automatic IKS worker replacement as a response to a certain metric (classic or VPC infrastructure)

While operating IBM Kubernetes (IKS) clusters (classsic infrastructure) we have run several times into a situation where IKS worker nodes start under-performing. We notice performance issues that are usually visible as:

  • Read timeouts while performing intense read operations via network from other applications running in our IKS cluster.

  • High IOWait metrics at worker pool level that we notice because we capture worker level OS metrics in all our worker nodes.

Such events happen at least once a month in our IKS clusters.

These problems are most of the time worked around by:

  • Cordoning the worker node

  • Draining the worker node

  • Waiting for auto-scaler to trigger a scale out event

  • Allowing IKS to add the new worker node in the relevant worker pool (it takes around 10 minutes to spin up a new VSI)

  • Remove the cordoned node from the IKS cluster

It would be really useful if IKS could handle these sort of events with an auto healing feature. And example of such feature is how Auto-Scaling Groups at AWS react when an instance fails its configured health check. Such feature is described at

Idea priority High
Needed By Quarter