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
What is your proposal:
injections in runtime hooks of koordlet such as cpu qos,memory oqs,llc/mba can work with or without runtime-hook-manager(runtime-porxy mode)
Why is this needed:
someone would rather use bypass-injection mode than changing kubelet cri endpoint config.
Is there a suggested solution, if so, please add it:
runtime hooks in koordlet should support two running mode: injection(with cri proxy),bypass(without cri proxy)
The text was updated successfully, but these errors were encountered:
What is your proposal:
injections in runtime hooks of koordlet such as cpu qos,memory oqs,llc/mba can work with or without runtime-hook-manager(runtime-porxy mode)
Why is this needed:
someone would rather use bypass-injection mode than changing kubelet cri endpoint config.
Is there a suggested solution, if so, please add it:
runtime hooks in koordlet should support two running mode: injection(with cri proxy),bypass(without cri proxy)
The text was updated successfully, but these errors were encountered: