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

Conversation

@LilyaBu
Copy link
Contributor

@LilyaBu LilyaBu commented Aug 29, 2019

Repatch extended resource cmk.intel.com/exclusive-cores after kubelet restart.

Since 1.10 version of Kubernetes Kubelet sets extended resource
capacity to zero after it restarts. To repatch extended resource
cmk.intel.com/exclusive-cores "discovery" container added to
reconcile-report daemonset.

@LilyaBu LilyaBu force-pushed the SOWC-228-fix-reboot-248 branch 4 times, most recently from a6dfd1c to d4fbc7c Compare September 4, 2019 09:59
… restart.

Since 1.10 version of Kubernetes Kubelet sets extended resource
capacity to zero after it restarts. To repatch extended resource
cmk.intel.com/exclusive-cores "discovery" container added to
reconcile-report daemonset.

Signed-off-by: Liliia Butorina <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant