Skip to Main Content
Cloud Management 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
Created by Guest
Created on Jan 2, 2025

Historical reporting capabilities for Kubernetes internal Cloud workstations

We would like the ability to identify, by running a report or a query, to see if an existing Kubernetes internal Cloud workstation is currently being used. We are specifically looking for historical information on:

(1) the last time the agent was linked up in the plan.

(2) is the agent currently being used if it's not linked up in the plan. Are there any batch objects in the DB defined to the workstation.

We are trying to determine if a Kubernetes workstation is no longer being used - for a way to determine if the workstation can be decommission. We do not have access to the Kubernetes workstation, so we are looking for a way we can run a process to identify and provide a summary of all the historical information to be able to determine if the agent can be decommissioned.

The benefits include:

(1) Identifying, via a report summary, to help us determine when Kubernetes agents are no longer being used.

(2) This would automate manually performing all the various conman and composer commands to collect this type of information, saving the number of hours collecting the information manually.

(3) This would satisfy audit requirements.

(4) Seems this feature would be helpful to other organizations running Kubernetes workstations in their environment.



Idea priority Medium