Skip to Main Content
Cloud Management and AIOps

This is an IBM Automation portal for Cloud Management and AIOps 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. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Workspace IBM Turbonomic ARM
Created by Guest
Created on Oct 4, 2023

Ability to set a Maximum Utilization Constraint for nodes in OCP/K8s clusters

As a customer, I need to be able to set a maximum utilization I don't want to pass for nodes, regarding the sum of all requests of all pods running there. Use case is: for production environment, I want to be sure to have enough capacity to retrieve workloads of a whole cluster if I'm losing half the cluster (for HA reason, resiliency when I'm losing a part of my DC or anything).

Idea priority Medium
  • Admin
    Eva Tuczai
    Oct 6, 2023

    This feature has merit for maintaining HA within a node, and is promoted for future consideration in 2024. The approach will be to provide the user a way to express a desired utilization that will impact pod moves but also when nodes should provision or suspend.

    Phase 1 we can look at providing this "knob" per VM/node or group of VMs/nodes.

    In Phase 2 if applicable we can look at defining per cluster.

  • Guest
    Oct 4, 2023

    I need this for each NodePool.