Inplace Pod Resizeing

In Place pod resizing

In place pod resizing comes to beta with kubernetes 1.33. Docs to specify how to go setup a resize restart policy, which indicates if a container should be restarted for the additional resource to be used. This isimportant since other than the benefit of starting the container on the same node with resize restart, it would give negligible benefit from the current Vertical Pod Scaling.

Issue opened with go so that GOMAXPROCS can be set more dynamically so that it does not need a restart.

This inplace scaling is being added to VPA.

Here is an example of this usage for increasing the CPU during the start of a JVM application. While the same cannot be done with memory.

Nodejs should be able to handle these changes without restarts.

This was a feature which was introduced in 1.27 as alpha and has undergone a lot of changes when it came to beta

Need to still figure out how this will affect binpacking the containers and how to best decide how to best utilize the nodes resources with the ability to have as little headroom as necessary but still enable this.