Skip to content

Commit baba0be

Browse files
authored
Merge pull request #80138 from dfitzmau/OCPBUGS-38002
/lgtm OCPBUGS-38002: Updated EggressIPconfig object to match API description
2 parents 4eedfbc + 3cca3af commit baba0be

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

modules/nw-egress-ips-config-object.adoc

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -3,12 +3,15 @@
33
// * networking/ovn_kubernetes_network_provider/assigning-egress-ips-ovn.adoc
44

55
[id="nw-egress-ips-config-object_{context}"]
6-
= EgressIPconfig object
7-
As a feature of egress IP, the `reachabilityTotalTimeoutSeconds` parameter configures the total timeout for checks that are sent by probes to egress IP nodes. The `egressIPConfig` object allows users to set the `reachabilityTotalTimeoutSeconds` `spec`. If the EgressIP node cannot be reached within this timeout, the node is declared down.
6+
= The egressIPConfig object
87

9-
You can increase this value if your network is not stable enough to handle the current default value of 1 second.
8+
As a feature of egress IP, the `reachabilityTotalTimeoutSeconds` parameter configures the EgressIP node reachability check total timeout in seconds. If the EgressIP node cannot be reached within this timeout, the node is declared down.
109

11-
The following YAML describes changing the `reachabilityTotalTimeoutSeconds` from the default 1 second probes to 5 second probes:
10+
You can set a value for the `reachabilityTotalTimeoutSeconds` in the configuration file for the `egressIPConfig` object. Setting a large value might cause the EgressIP implementation to react slowly to node changes. The implementation reacts slowly for EgressIP nodes that have an issue and are unreachable.
11+
12+
If you omit the `reachabilityTotalTimeoutSeconds` parameter from the `egressIPConfig` object, the platform chooses a reasonable default value, which is subject to change over time. The current default is `1` second. A value of `0` disables the reachability check for the EgressIP node.
13+
14+
The following `egressIPConfig` object describes changing the `reachabilityTotalTimeoutSeconds` from the default `1` second probes to `5` second probes:
1215

1316
[source,yaml]
1417
----
@@ -28,8 +31,5 @@ spec:
2831
routingViaHost: false
2932
genevePort: 6081
3033
----
31-
<1> The `egressIPConfig` holds the configurations for the options of the `EgressIP` object. Changing these configurations allows you to extend the `EgressIP` object.
32-
33-
<2> The value for `reachabilityTotalTimeoutSeconds` accepts integer values from `0` to `60`. A value of 0 disables the reachability check of the egressIP node. Values of `1` to `60` correspond to the duration in seconds between probes sending the reachability check for the node.
34-
35-
34+
<1> The `egressIPConfig` holds the configurations for the options of the `EgressIP` object. By changing these configurations, you can extend the `EgressIP` object.
35+
<2> The value for `reachabilityTotalTimeoutSeconds` accepts integer values from `0` to `60`. A value of `0` disables the reachability check of the egressIP node. Setting a value from `1` to `60` corresponds to the timeout in seconds for a probe to send the reachability check to the node.

0 commit comments

Comments
 (0)