This is an IBM Automation portal for Cloud Management 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 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, cloud):
Cloud Pak for Multicloud Management
Cloud Pak for Network Automation - including Orchestration and Performance Management
Cloud Pak for Watson AIOps - including Netcool Operations Management portfolio
Edge Application Manager
IBM Observability with Instana
ITM-APM Products - including IBM Tivoli Monitoring v6 and Application Performance Monitoring v8
Workload Automation - including Workload Scheduler
Tivoli System Automation - including Tivoli System Automation Application Manager (SA AM), Tivoli System Automation for Multiplatforms (SA MP)
Vertical scaling of Application and Event monitoring stateful services
A means by which to effectively perform vertical scaling of key stateful services in the `ibm-cloud-appmgmt-prod` chart.
Today, the stateful services include PersistentVolumeClaims in their pod spec, and use helm values to configure the size of the claims per pod. As such, horizontal scaling is handled by the addition of more replicas in the statefulset.
The PersistentVolumeClaim fields in the statefulset pod spec are immutable. Changing the claimed storage size by changing the helm values leads to a failed release due to immutable fields. This prevents the user from vertically scaling their stateful services through the means of the helm release.
If a user has `200Gi` claims per pod can only scale with additional replicas adding `200Gi` at a time and the overhead of more replicas.
In a number of cases, it would make more sense to vertically scale the claims such that each claim is `1000Gi`
Today, any means taken to vertically scale these stateful services would be disconnected from the helm release and its configured values.
Investing in maturing the stateful services to be controlled by operators could address this, in addition to other administrative needs for stateful services.
Do not place IBM confidential, company confidential, or personal information into any field.