Skip to Main Content
Shape the future of IBM watsonx Orchestrate

Start by searching and reviewing ideas others have posted, and add a comment (private if needed), vote, or subscribe to updates on them if they matter to you.

If you can't find what you are looking for, create a new idea:

  1. stick to one feature enhancement per idea

  2. add as much detail as possible, including use-case, examples & screenshots (put anything confidential in Hidden details field or a private comment)

  3. Explain business impact and timeline of project being affected

[For IBMers] Add customer/project name, details & timeline in Hidden details field or a private comment (only visible to you and the IBM product team).

This all helps to scope and prioritize your idea among many other good ones. Thank you for your feedback!

Specific links you will want to bookmark for future use
Learn more about IBM watsonx Orchestrate - Use this site to find out additional information and details about the product.
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
Created by Guest
Created on May 11, 2026

Custom sizing ConfigMap for non-prod deployment

1. Provide a custom sizing ConfigMap appropriate for a nonprod/staging/demo deployment with the following profile:

- CP4AIOps 4.13 with aiopsFoundation, applicationManager, aiManager modules

- WXO 7.1.0 in agentic mode - Steady-state usage (demo/testing, not production traffic)

- Target: reduce CPU requests to 2-3x actual usage instead of 16.8x

2. Document the format of the aiops-custom-size-profile ConfigMap so we can create and maintain our own sizing profiles without requiring a support case for each environment.

3. Document the WXO CR-level resource override mechanism that MANU referenced, so we can adjust WXO component sizing independently.

Idea priority High