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.
Specific links you will want to bookmark for future use
Create alternative container rightsizing action execution to directly update pod resource
The idea is mimc vertical pod autoscaler (VPA https://github.com/kubernetes/autoscaler/tree/master/vertical-pod-autoscaler) initial mode.
"Initial": VPA only assigns resource requests on pod creation and never changes them later.
This is just another way to apply the recommended actions for resize (vertical only) when pods are created. What is nice about this approach would be that we don't need to update the source of truth since the original Deployment/Statefulset/Daemonset/etc will be untouched, only the pod runtime settings will be changed with a mutating webhook. The challenge would be to persist/cache recommended sizes on the remote clusters so that the webhook is as quick as possible.
The feature under consideration is to provide alternative mechanisms to apply Container Spec rightsizing actions in a k8s cluster. Today the OOTB mechanism involves updating the parent controller, which is a good strategy to persist and propagate the change across all replicas. However k8s does provide alternatives that could be useful options for those that want to operationalize Turbo without changing the parent definition.
Under consideration that will be handled in separate Master Epics:
Provide a Turbo mutating webhook to be used in versions of k8s until in-place pod update is beta. Here Turbonomic should improve of what VPA does and apply the change to all running replicas, given that our analysis is designed to provide a better definition of consistent scaling across all replicas.
Do not place IBM confidential, company confidential, or personal information into any field.