cmk can't working in kubernetes init-container about cpu-manager-for-kubernetes HOT 5 CLOSED

@przemeklal got it, it's clear now, thank you very much!

from cpu-manager-for-kubernetes.

Thanks for raising this issue! As you correctly pointed out, the admission hook is not adding the necessary mounts etc. to the init containers and just looks at the containers.

We will add this as an issue to solve in our backlog!

If you have a pressing need to use init containers with CMK you could manually add in the necessary details to the init container for now.

from cpu-manager-for-kubernetes.

thank you for your response, We are very much looking forward to the introduction of this new feature.
at this moment, could you show us the detail about which filed and what information is necessary for CMK that can add to deployment YAML file? any guide document for it?

from cpu-manager-for-kubernetes.

Hi @nokia-t1zhou, the bare minimum example is available here (except for the service account).

You're going to need 3 volumes/volume mounts - CMK conf dir, CMK bin dir and /proc fs mounted from the host - and the env variable pointing to the mounted host /proc fs. You can also request CMK exclusive core resources if you plan to use the exclusive pool.

from cpu-manager-for-kubernetes.

@nokia-t1zhou fixed and merged

from cpu-manager-for-kubernetes.