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 Under review
Workspace Instana
Categories Self Hosted
Created by Guest
Created on Aug 20, 2026

Instana (k3s-pods) CPU and MEMORY reservation(requests) at startup is much too high in relation to the real utilization. Results in high number of CPU/MEM at startup which is not used in running state. (Expensive resources)

We are using the self-hosted Instana Standard edition (k3s). More than once we have problems with messages like too less CPU to startup (pending pods). Several times we added CPU but what we see is that when it is running in production the utilization of CPU does not exceed 15% of all the available CPU because of the count of the configured CPU-request of all the pods is very high configured which is not used at running time. For memory the same but is the utilization a bit higher (35 %). A support request to tune this better and bring requests more in balance with real utilization will decrease the CPU/MEM allocation without decreasing performance. Now there is 85% wasted CPU allocation and 65% MEM.

Idea priority Urgent