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
{{ message }}
This repository was archived by the owner on Jan 18, 2023. It is now read-only.
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.
Signed-off-by: Liliia Butorina <[email protected]>
Copy file name to clipboardExpand all lines: docs/html/docs/operator.html
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -617,7 +617,7 @@ <h2>
617
617
the recommended way to start troubleshooting is to look at the logs using <code>kubectl logs POD_NAME [CONTAINER_NAME] -f</code>.</p>
618
618
<p>For example, assuming you ran the <a href="../resources/pods/cmk-cluster-init-pod.yaml">cmk-cluster-init-pod template</a> with default options, it
619
619
should create two pods on each node named <code>cmk-init-install-discover-pod-<node-name></code> and
620
-
<code>cmk-reconcile-nodereport-<node-name></code>, where <code><node-name></code> should be replaced with the name of the node.</p>
620
+
<code>cmk-rediscover-reconcile-nodereport-<node-name></code>, where <code><node-name></code> should be replaced with the name of the node.</p>
621
621
<p>If you want to look at the logs from the container which ran the <code>discover</code> subcommand in the pod, you can use
0 commit comments