This is an IBM Automation portal for Digital Business Automation 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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Please use the following category to raise ideas for these offerings for all environments (traditional on premises, containers, on cloud):
Cloud Pak for Automation - including Business Automation Studio, Business Automation Insights
Business Automation Workflow (BAW) - including BAW, Business Process Manager, Workstream Services, Business Performance Center, Advanced Case Management
Content and Capture Services - including Filenet, Automation Document Processing, Daeja, Navigator, Content Collector, Enterprise Records, Business Automation Content Analyzer, Datacap, Automation Mobile Capture, Content Manager OnDemand, IBM Content Manager
Automation Decision Services (ADS) - including ADS, Operational Decision Manager
Robotic Process Automation
Robotic Process Automation with Automation Anywhere
IBM Blueworks Live
Specific links you will want to bookmark for future use
Enable Horizontal Pod Autoscaler support for ODM Decision Server Runtime under ICP4BA
In a Kubernetes/OpenShift deployment, the number of replicas for the Decision Server Runtime deployment is a fixed amount defined in the ICP4ACluster custom resource. The ICP4BA operator enforces this fixed amount by resetting any changes made to the Deployment configuration.
A Horizontal Pod Autoscaler configuration works by monitoring metrics and updating the Deployment configuration with a new replica count when a decision is made to adjust the number of pods. However, when the ICP4BA operator is running, any changes to the Deployment are reset.
The new feature I would like to see is to have the ability to define the settings for the Horizontal Pod Autoscaler in the custom resource and when configured, the operator should not update the replica count in the Deployment configuration during its reconciliation phase.
Enabling this feature will allow more flexibility to manage cluster resources and meet spikes in workload.
Do not place IBM confidential, company confidential, or personal information into any field.