Skip to content
This repository has been archived by the owner on Jan 18, 2023. It is now read-only.

k8s node loses CMK exclusive-cores property after reboot #248

Open
psiwczak opened this issue Jul 9, 2019 · 1 comment
Open

k8s node loses CMK exclusive-cores property after reboot #248

psiwczak opened this issue Jul 9, 2019 · 1 comment

Comments

@psiwczak
Copy link

psiwczak commented Jul 9, 2019

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
@LilyaBu
Copy link
Contributor

LilyaBu commented Aug 29, 2019

pull request created #252
solution with minimal changes.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants