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
This results to K8s failure to throttle pod so that it follows resized CPU limit on minikube when cri-dockerd is used.
InPlacePodVerticalScaling in K8s is soon going to reach Beta and luck of such support from cri-dockerd means that end users will face this limitation as described kubernetes/kubernetes#118371 in minikube if cri-dockerd is used.
The text was updated successfully, but these errors were encountered:
As far as I know, having Docker support was not a blocker for KEP-1287
As of Kubernetes v1.20, the CRI has included support for in-place resizing of containers via the UpdateContainerResources API, which is implemented by both containerd and CRI-O
So I am not sure that the feature will ever be implemented for Docker?
cri-dockerd does not set Resources to ContainerStatus code
For comparison containerd sets it code
This results to K8s failure to throttle pod so that it follows resized CPU limit on minikube when cri-dockerd is used.
InPlacePodVerticalScaling in K8s is soon going to reach Beta and luck of such support from cri-dockerd means that end users will face this limitation as described kubernetes/kubernetes#118371 in minikube if cri-dockerd is used.
The text was updated successfully, but these errors were encountered: