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
Copy file name to clipboardExpand all lines: modules/k8s-best-practices-platform-upgrade.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,7 +52,7 @@ spec:
52
52
app: db
53
53
----
54
54
55
-
See link:https://docs.openshift.com/container-platform/latest/scalability_and_performance/index.html[Recommended performance and scalability practices].
55
+
See link:https://docs.openshift.com/container-platform/latest/scalability_and_performance/index.html[recommended performance and scalability practices].
56
56
57
57
By default, only one machine is allowed to be unavailable when applying the kubelet-related configuration to the available worker nodes. For a large cluster, it can take a long time for the configuration change to be reflected. At any time, you can adjust the number of machines that are updating to speed up the process.
0 commit comments