This repository was archived by the owner on Jan 18, 2023. It is now read-only.
This repository was archived by the owner on Jan 18, 2023. It is now read-only.
k8s node loses CMK exclusive-cores property after reboot #248
Open
Description
After reboot - K8S compute nodes seem to be losing the cmk-related resource properties:
Before reboot:
"cmk.intel.com/exclusive-cores": "1"
After reboot
"cmk.intel.com/exclusive-cores": "0"
I need to rerun the CMK init & discovery pod for the situation to get back to normal.
Steps to reproduce:
- set up CMK on the k8s compute node
- reboot the node
Steps to fix:
- delete the pods: cmk-cluster-init-pod , cmk-init-install-discover-pod-*
- delete /etc/cmk directory
- reapply the cmk cluster-init pod
Metadata
Metadata
Assignees
Labels
No labels