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
The runtime hook CPUSetAllocator in the koordlet is responsible for binding CPUs for pods following the scheduling result. However, it ignores the init containers due to historical performance and timeliness issues.
After the native sidecar container feature is introduced to Kubernetes 1.28, init containers of a pod can be long-running if they set restartPolicy as Always.
To properly manage the resources of the sidecar containers, the runtime hooks should reconsider the init containers.
Why is this needed:
Is there a suggested solution, if so, please add it:
The text was updated successfully, but these errors were encountered:
What is your proposal:
The runtime hook CPUSetAllocator in the koordlet is responsible for binding CPUs for pods following the scheduling result. However, it ignores the init containers due to historical performance and timeliness issues.
After the native sidecar container feature is introduced to Kubernetes 1.28, init containers of a pod can be long-running if they set restartPolicy as
Always
.To properly manage the resources of the sidecar containers, the runtime hooks should reconsider the init containers.
Why is this needed:
Is there a suggested solution, if so, please add it:
The text was updated successfully, but these errors were encountered: