Skip to content

Commit 9241de9

Browse files
committed
OSDOCS-3501: add clb timeouts and restructure
1 parent 6078fae commit 9241de9

11 files changed

+107
-33
lines changed

_topic_maps/_topic_map.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1153,8 +1153,8 @@ Topics:
11531153
- Name: Configuring ingress cluster traffic using a load balancer
11541154
File: configuring-ingress-cluster-traffic-load-balancer
11551155
Distros: openshift-enterprise,openshift-origin
1156-
- Name: Configuring ingress cluster traffic on AWS using a Network Load Balancer
1157-
File: configuring-ingress-cluster-traffic-aws-network-load-balancer
1156+
- Name: Configuring ingress cluster traffic on AWS
1157+
File: configuring-ingress-cluster-traffic-aws
11581158
Distros: openshift-enterprise,openshift-origin
11591159
- Name: Configuring ingress cluster traffic using a service external IP
11601160
File: configuring-ingress-cluster-traffic-service-external-ip

installing/installing_aws/installing-aws-network-customizations.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ include::modules/nw-modifying-operator-install-config.adoc[leveloffset=+1]
5757

5858
[NOTE]
5959
====
60-
For more information on using a Network Load Balancer (NLB) on AWS, see xref:../../networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws-network-load-balancer.adoc#configuring-ingress-cluster-traffic-aws-network-load-balancer[Configuring Ingress cluster traffic on AWS using a Network Load Balancer].
60+
For more information on using a Network Load Balancer (NLB) on AWS, see xref:../../networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws.adoc#configuring-ingress-cluster-traffic-aws-network-load-balancer[Configuring Ingress cluster traffic on AWS using a Network Load Balancer].
6161
====
6262

6363
include::modules/nw-aws-nlb-new-cluster.adoc[leveloffset=+1]

modules/nw-aws-nlb-existing-cluster.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
// Module included in the following assemblies:
22
//
3-
// * networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws-network-load-balancer.adoc
3+
// * networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws.adoc
44

55
:_content-type: PROCEDURE
66
[id="nw-aws-nlb-existing-cluster_{context}"]

modules/nw-aws-nlb-new-cluster.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
// Module included in the following assemblies:
22
//
33
// * installing/installing_aws/installing-aws-network-customizations.adoc
4-
// * networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws-network-load-balancer.adoc
4+
// * networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws.adoc
55

66
:_content-type: PROCEDURE
77
[id="nw-aws-nlb-new-cluster_{context}"]

modules/nw-aws-replacing-clb-with-nlb.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
// Module included in the following assemblies:
22
//
3-
// * networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws-network-load-balancer.adoc
3+
// * networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws.adoc
44

55
:_content-type: PROCEDURE
66
[id="nw-aws-replacing-clb-with-nlb_{context}"]
Lines changed: 42 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,42 @@
1+
// Modules included in the following assemblies:
2+
//
3+
// * networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws.adoc
4+
5+
:_content-type: PROCEDURE
6+
[id="nw-configuring-clb-timeouts_{context}"]
7+
= Configuring Classic Load Balancer timeouts
8+
9+
You can configure the default timeouts for a Classic Load Balancer (CLB) to extend idle connections.
10+
11+
.Prerequisites
12+
13+
* You must have a deployed Ingress Controller on a running cluster.
14+
15+
.Procedure
16+
17+
. Set an AWS connection idle timeout of five minutes for the default `ingresscontroller` by running the following command:
18+
+
19+
[source,terminal]
20+
----
21+
$ oc -n openshift-ingress-operator patch ingresscontroller/default \
22+
--type=merge --patch='{"spec":{"endpointPublishingStrategy": \
23+
{"type":"LoadBalancerService", "loadBalancer": \
24+
{"scope":"External", "providerParameters":{"type":"AWS", "aws": \
25+
{"type":"Classic", "classicLoadBalancer": \
26+
{"connectionIdleTimeout":"5m"}}}}}}}'
27+
----
28+
29+
. Optional: Restore the default value of the timeout by running the following command:
30+
+
31+
[source,terminal]
32+
----
33+
$ oc -n openshift-ingress-operator patch ingresscontroller/default \
34+
--type=merge --patch='{"spec":{"endpointPublishingStrategy": \
35+
{"loadBalancer":{"providerParameters":{"aws":{"classicLoadBalancer": \
36+
{"connectionIdleTimeout":null}}}}}}}'
37+
----
38+
39+
[NOTE]
40+
====
41+
You must specify the `scope` field when you change the connection timeout value unless the current scope is already set. When you set the `scope` field, you do not need to do so again if you restore the default timeout value.
42+
====
Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws.adoc
4+
5+
:_content-type: CONCEPT
6+
[id="nw-configuring-elb-timeouts-aws-classic_{context}"]
7+
= Configuring Classic Load Balancer timeouts on AWS
8+
9+
{product-title} provides a method for setting a custom timeout period for a specific route or Ingress Controller. Additionally, an AWS Classic Load Balancer (CLB) has its own timeout period with a default time of 60 seconds.
10+
11+
If the timeout period of the CLB is shorter than the route timeout or Ingress Controller timeout, the load balancer can prematurely terminate the connection. You can prevent this problem by increasing both the timeout period of the route and CLB.
Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws.adoc
4+
5+
:_content-type: CONCEPT
6+
[id="nw-configuring-ingress-cluster-traffic-aws-network-load-balancer_{context}"]
7+
= Configuring ingress cluster traffic on AWS using a Network Load Balancer
8+
9+
{product-title} provides methods for communicating from outside the cluster with services that run in the cluster. One such method uses a Network Load Balancer (NLB). You can configure an NLB on a new or existing AWS cluster.

modules/nw-configuring-route-timeouts.adoc

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,7 @@
11
// Module filename: nw-configuring-route-timeouts.adoc
22
// Module included in the following assemblies:
33
// * networking/configuring-routing.adoc
4+
// * networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws.adoc
45

56
:_content-type: PROCEDURE
67
[id="nw-configuring-route-timeouts_{context}"]

networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-aws-network-load-balancer.adoc

Lines changed: 0 additions & 27 deletions
This file was deleted.

0 commit comments

Comments
 (0)