1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Files
openshift-docs/modules/nodes-cluster-worker-latency-profiles-examining.adoc
2025-11-12 12:08:26 +00:00

67 lines
1.6 KiB
Plaintext
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
// Module included in the following assemblies:
//
// scalability_and_performance/scaling-worker-latency-profiles.adoc
:_mod-docs-content-type: PROCEDURE
[id="nodes-cluster-worker-latency-profiles-examining_{context}"]
= Example steps for displaying resulting values of workerLatencyProfile
You can display the values in the `workerLatencyProfile` with the following commands.
.Verification
. Check the `default-not-ready-toleration-seconds` and `default-unreachable-toleration-seconds` fields output by the Kube API Server:
+
[source,terminal]
----
$ oc get KubeAPIServer -o yaml | grep -A 1 default-
----
+
.Example output
[source,terminal]
----
default-not-ready-toleration-seconds:
- "300"
default-unreachable-toleration-seconds:
- "300"
----
. Check the values of the `node-monitor-grace-period` field from the Kube Controller Manager:
+
[source,terminal]
----
$ oc get KubeControllerManager -o yaml | grep -A 1 node-monitor
----
+
.Example output
[source,terminal]
----
node-monitor-grace-period:
- 40s
----
. Check the `nodeStatusUpdateFrequency` value from the Kubelet. Set the directory `/host` as the root directory within the debug shell. By changing the root directory to `/host`, you can run binaries contained in the hosts executable paths:
+
[source,terminal]
----
$ oc debug node/<worker-node-name>
----
+
[source,terminal]
----
$ chroot /host
----
+
[source,terminal]
----
# cat /etc/kubernetes/kubelet.conf|grep nodeStatusUpdateFrequency
----
+
.Example output
[source,terminal]
----
“nodeStatusUpdateFrequency”: “10s”
----
These outputs validate the set of timing variables for the Worker Latency Profile.