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 Future consideration
Workspace Cloudability
Created by Guest
Created on Aug 19, 2026

Add GPU and GPU memory to container cost allocation

We need Cloudability Kubernetes Cost Allocation to include GPU and GPU memory weighted by GPU importance along other existing metrics (CPU, Memory, Disk, Network) and COST measures in Cloudability Dashboards+Reports properly reflect allocation

Today, Cloudability provides Kubernetes Cost Allocation for K8S clusters running agent and the applications/pod COSTS are properly allocated based on the resource usage (CPU, memory, disk, i/o). The COSTS can be shown in the Cloudability Reports, Dashboards, and Explore resources used by FINANCE and ENGINEERING teams. This is helpful and good for traditional non-GPU workloads.

AIML workloads often require GPU based instances that run workloads in Kubernetes; however, according to our TAM, the GPU and GPU memory are not included in the Cloudability Cost allocation and so the COSTS reports in REPORTS, DASHBOARDS, EXPLORES does not properly allocate the costs for these very expensive GPU servers. Rough estimates are that Cost Allocation is off by 30-50% for GPU enabled AWS instances (P and G instance families like the p5.48xlarge). While some of that data may be available in KubeCost, that is not the core tool used by Finance processes.

Idea priority High
  • Guest
    Sep 16, 2026

    Please note that Kubecost/Cloudability Advanced Containers which opens a separate UI while helpful does not include the DASHBOARDS and REPORTS in CLOUDABILITY that are used by FINANCE and most ENGINEERING teams. Need the Cost Attribution for Kubernetes to be integrated with Cloudability REPORTS and EXPLORE and DASHBOARDS like it is today for K8S CPU + MEMORY as well as GPU and GPU MEMORY.

  • Admin
    Chip Zoller
    Sep 15, 2026

    As mentioned, GPU costs and even more is available in Kubecost/Cloudability Advanced Containers with more enhancements planned in that area.