Skip to Main Content
Cloud and AIOps


This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation 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 (https://ideas.ibm.com).

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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

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

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Submitted
Workspace IBM Turbonomic ARM
Categories Reporting
Created by Guest
Created on Jun 12, 2026

Add Kubernetes Worker Node Mapping to Container Reports

Currently, Container Resize reports provide information such as:

  • Namespace
  • Deployment / Workload
  • Resource requests and limits
  • Resize recommendations

However, there is no way to include the Kubernetes Worker Node on which the workload is currently running.
Although Turbonomic already understands workload placement within Kubernetes clusters, this information is currently not available in reporting and analytics.

This makes capacity planning and operational analysis more difficult because users cannot easily determine:

  • Which worker nodes are hosting workloads with resize recommendations
  • How recommendations are distributed across the cluster
  • What impact resizing workloads may have on individual worker nodes
  • Which nodes are potentially overutilized or underutilized due to workload placement

Requested enhancement

Add workload-to-node relationship data to reporting and analytics, allowing reports to include fields such as:

  • Cluster
  • Namespace
  • Deployment / StatefulSet / Workload
  • Current Worker Node
  • CPU Request
  • Memory Request
  • CPU Recommendation
  • Memory Recommendation

Example

Namespace

Deployment

Worker Node

Recommendation

prod

frontend

worker-01

Resize Down

prod

api

worker-03

Resize Up

This would significantly improve Kubernetes capacity planning, optimization analysis, troubleshooting, and reporting.

Idea priority High