Skip to content

Commit 51cfd82

Browse files
authored
Merge pull request #47973 from mburke5678/nodes-workerlatencyprofile-edge
OCPNODE-638: Kubelet-Controller Manager communication Profiles (WorkerLatencyProfiles) Add to Edge docs
2 parents 1dee6a9 + 72136eb commit 51cfd82

File tree

4 files changed

+42
-2
lines changed

4 files changed

+42
-2
lines changed

_topic_maps/_topic_map.yml

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2259,6 +2259,9 @@ Topics:
22592259
- Name: Low latency tuning
22602260
File: cnf-low-latency-tuning
22612261
Distros: openshift-origin,openshift-enterprise
2262+
- Name: Improving cluster stability in high latency environments using worker latency profiles
2263+
File: scaling-worker-latency-profiles
2264+
Distros: openshift-origin,openshift-enterprise
22622265
- Name: Creating a performance profile
22632266
File: cnf-create-performance-profiles
22642267
Distros: openshift-origin,openshift-enterprise

nodes/edge/nodes-edge-remote-workers.adoc

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ However, having remote worker nodes can introduce higher latency, intermittent l
1717
1818
* *Power outage*: Because the control plane and remote worker nodes are in separate locations, a power outage at the remote location or at any point between the two can negatively impact your cluster. See xref:../../nodes/edge/nodes-edge-remote-workers.adoc#nodes-edge-remote-workers-power_nodes-edge-remote-workers[Power loss on remote worker nodes] for information on how {product-title} responds to a node losing power and for methods to diminish the impact to your cluster.
1919
20-
* *Latency spikes or temporary reduction in throughput*: As with any network, any changes in network conditions between your cluster and the remote worker nodes can negatively impact your cluster. These types of situations are beyond the scope of this documentation.
20+
* *Latency spikes or temporary reduction in throughput*: As with any network, any changes in network conditions between your cluster and the remote worker nodes can negatively impact your cluster. {product-title} offers multiple _worker latency profiles_ that let you control the reaction of the cluster to latency issues.
2121
2222
Note the following limitations when planning a cluster with remote worker nodes:
2323

@@ -37,6 +37,15 @@ include::modules/nodes-edge-remote-workers-power.adoc[leveloffset=+1]
3737

3838
For more information on using these objects in a cluster with remote worker nodes, see xref:../../nodes/edge/nodes-edge-remote-workers.html#nodes-edge-remote-workers-strategies_nodes-edge-remote-workers[About remote worker node strategies].
3939

40+
[id="nodes-edge-remote-workers-latency"]
41+
== Latency spikes or temporary reduction in throughput to remote workers
42+
43+
include::snippets/worker-latency-profile-intro.adoc[]
44+
45+
.Additional resources
46+
47+
* xref:../../nodes/clusters/nodes-cluster-worker-latency-profiles.adoc#nodes-cluster-worker-latency-profiles[Improving cluster stability in high latency environments using worker latency profiles ]
48+
4049
include::modules/nodes-edge-remote-workers-strategies.adoc[leveloffset=+1]
4150

4251
[role="_additional-resources"]

scalability_and_performance/optimizing-networking.adoc

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,8 +32,10 @@ include::modules/recommended-install-practices.adoc[leveloffset=+1]
3232
include::modules/ipsec-impact-networking.adoc[leveloffset=+1]
3333

3434
[role="_additional-resources"]
35-
.Additional resources
35+
[id="optimizing-networking-additional-resources"]
36+
== Additional resources
3637

3738
* xref:../installing/installing_aws/installing-aws-network-customizations.adoc#modifying-nwoperator-config-startup_installing-aws-network-customizations[Modifying advanced network configuration parameters]
3839
* xref:../networking/cluster-network-operator.adoc#nw-operator-configuration-parameters-for-ovn-sdn_cluster-network-operator[Configuration parameters for the OVN-Kubernetes default CNI network provider]
3940
* xref:../networking/cluster-network-operator.adoc#nw-operator-configuration-parameters-for-openshift-sdn_cluster-network-operator[Configuration parameters for the OpenShift SDN default CNI network provider]
41+
* xref:../scalability_and_performance/scaling-worker-latency-profiles.adoc#scaling-worker-latency-profiles[Improving cluster stability in high latency environments using worker latency profiles]
Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
:_content-type: ASSEMBLY
2+
:context: scaling-worker-latency-profiles
3+
[id="scaling-worker-latency-profiles"]
4+
= Improving cluster stability in high latency environments using worker latency profiles
5+
include::_attributes/common-attributes.adoc[]
6+
7+
toc::[]
8+
9+
10+
11+
// The following include statements pull in the module files that comprise
12+
// the assembly. Include any combination of concept, procedure, or reference
13+
// modules required to cover the user story. You can also include other
14+
// assemblies.
15+
16+
17+
include::snippets/worker-latency-profile-intro.adoc[]
18+
19+
These worker latency profiles are three sets of parameters that are pre-defined with carefully tuned values that control the reaction of the cluster to latency issues without your needing to determine the best values manually.
20+
21+
You can configure worker latency profiles when installing a cluster or at any time you notice increased latency in your cluster network.
22+
23+
include::modules/nodes-cluster-worker-latency-profiles-about.adoc[leveloffset=+1]
24+
25+
include::modules/nodes-cluster-worker-latency-profiles-using.adoc[leveloffset=+1]
26+

0 commit comments

Comments
 (0)