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 Under review
Workspace IBM Turbonomic ARM
Created by Guest
Created on Apr 26, 2024

Kubernetes Migrate Workload plan improvements: Cost and Sharing

Turbonomic planning on kubernetes allows us to simulate scenarios to migrate workloads to different clusters to simulate how workloads could be supported on different node sizes.  This is a workaround to having Turbo recommend what vertical size node would be better for this workload.

The ask is:

1. allow plans to be shared via UI (roles restrict sharing)

2. allow this plan to be downloaded  - a one click button to save and share the whole plan in either pdf or excel format

3. make sure cost details are saved, even if the node pool used in the plan scenario no longer exists

For item # 3 what was observed was that cost data did not seem to be retained.  In this scenario, when we migrated workload to a cluster, the target cluster would have a node pool of nodes sized A.  Then we would delete that pool, create a node pool of size B, and re-run the plan.  Retrieving the plan from size A, it was observed that the cost information was gone, possibly because the node pool no longer existed.  As a user, I would expect cost data to be stored with the plan.

Idea priority Low