You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi "The planning component is essential for enabling Intent Driven Orchestration (IDO), as it will break down the higher- level objectives (e.g. a latency compliance targets) into dynamic actionable plans (e.g. policies for platform resource allocation, dynamic vertical & horizontal scaling, etc.)."
As we understand the in-place vertical scaling (i.e without having to restart kubernetes) of CPU resources is still not supported in Opensource Kubernetes. So, do you also plan to support the in-place scaling here or is the scope here is only to provide the IDO as a plugin ?
The text was updated successfully, but these errors were encountered:
The vertical scaling / setting resource allocations is something we want to do for sure, we are figuring out a plan for that atm. Also, note we don't want to go with something that K8s community would not support for in-place scaling. Should that capability be ready it is sth we certainly want to revisit.
Hi
"The planning component is essential for enabling Intent Driven Orchestration (IDO), as it will break down the higher- level objectives (e.g. a latency compliance targets) into dynamic actionable plans (e.g. policies for platform resource allocation, dynamic vertical & horizontal scaling, etc.)."
As we understand the in-place vertical scaling (i.e without having to restart kubernetes) of CPU resources is still not supported in Opensource Kubernetes. So, do you also plan to support the in-place scaling here or is the scope here is only to provide the IDO as a plugin ?
The text was updated successfully, but these errors were encountered: