Skip to content

Commit d93f6f2

Browse files
authored
Merge pull request #86647 from brendan-daly-red-hat/OCPBUGS-45011
OCPBUGS-45011#rearrange step order
2 parents 2b137e2 + 53c13a4 commit d93f6f2

File tree

1 file changed

+42
-42
lines changed

1 file changed

+42
-42
lines changed

modules/private-clusters-setting-api-private.adoc

Lines changed: 42 additions & 42 deletions
Original file line numberDiff line numberDiff line change
@@ -31,48 +31,6 @@ you can reconfigure the API server to use only the private zone.
3131
3232
.Procedure
3333

34-
. In the web portal or console for your cloud provider, take the following actions:
35-
36-
.. Locate and delete the appropriate load balancer component:
37-
ifndef::cpmso-using-azure[]
38-
*** For AWS, delete the external load balancer. The API DNS entry in the private zone already points to the internal load balancer, which uses an identical configuration, so you do not need to modify the internal load balancer.
39-
endif::cpmso-using-azure[]
40-
ifndef::cpmso-using-aws[]
41-
*** For Azure, delete the `api-internal-v4` rule for the public load balancer.
42-
43-
.. For Azure, configure the Ingress Controller endpoint publishing scope to `Internal`.
44-
For more information, see "Configuring the Ingress Controller endpoint publishing scope to Internal".
45-
46-
.. For the Azure public load balancer, if you configure the Ingress Controller endpoint publishing scope to `Internal` and there are no existing inbound rules in the public load balancer, you must create an outbound rule explicitly to provide outbound traffic for the backend address pool.
47-
For more information, see the Microsoft Azure documentation about adding outbound rules.
48-
endif::cpmso-using-aws[]
49-
50-
.. Delete the
51-
ifdef::cpmso-using-aws[`api.$clustername.$yourdomain`]
52-
ifdef::post-install[`api.$clustername.$yourdomain` or]
53-
ifndef::cpmso-using-aws[`api.$clustername`]
54-
DNS entry in the public zone.
55-
56-
ifdef::cpmso-using-aws[]
57-
. Remove the external load balancers by deleting the following indicated lines in the control plane machine set custom resource:
58-
+
59-
[source,yaml]
60-
----
61-
# ...
62-
providerSpec:
63-
value:
64-
# ...
65-
loadBalancers:
66-
- name: lk4pj-ext # <1>
67-
type: network # <2>
68-
- name: lk4pj-int
69-
type: network
70-
# ...
71-
----
72-
<1> Delete the `name` value for the external load balancer, which ends in `-ext`.
73-
<2> Delete the `type` value for the external load balancer.
74-
endif::cpmso-using-aws[]
75-
7634
ifdef::post-install[]
7735
. AWS clusters: Remove the external load balancers:
7836
+
@@ -155,6 +113,48 @@ providerSpec:
155113
.... Repeat this process for each of the control plane machines.
156114
endif::post-install[]
157115

116+
. In the web portal or console for your cloud provider, take the following actions:
117+
118+
.. Locate and delete the appropriate load balancer component:
119+
ifndef::cpmso-using-azure[]
120+
*** For AWS, delete the external load balancer. The API DNS entry in the private zone already points to the internal load balancer, which uses an identical configuration, so you do not need to modify the internal load balancer.
121+
endif::cpmso-using-azure[]
122+
ifndef::cpmso-using-aws[]
123+
*** For Azure, delete the `api-internal-v4` rule for the public load balancer.
124+
125+
.. For Azure, configure the Ingress Controller endpoint publishing scope to `Internal`.
126+
For more information, see "Configuring the Ingress Controller endpoint publishing scope to Internal".
127+
128+
.. For the Azure public load balancer, if you configure the Ingress Controller endpoint publishing scope to `Internal` and there are no existing inbound rules in the public load balancer, you must create an outbound rule explicitly to provide outbound traffic for the backend address pool.
129+
For more information, see the Microsoft Azure documentation about adding outbound rules.
130+
endif::cpmso-using-aws[]
131+
132+
.. Delete the
133+
ifdef::cpmso-using-aws[`api.$clustername.$yourdomain`]
134+
ifdef::post-install[`api.$clustername.$yourdomain` or]
135+
ifndef::cpmso-using-aws[`api.$clustername`]
136+
DNS entry in the public zone.
137+
138+
ifdef::cpmso-using-aws[]
139+
. Remove the external load balancers by deleting the following indicated lines in the control plane machine set custom resource:
140+
+
141+
[source,yaml]
142+
----
143+
# ...
144+
providerSpec:
145+
value:
146+
# ...
147+
loadBalancers:
148+
- name: lk4pj-ext # <1>
149+
type: network # <2>
150+
- name: lk4pj-int
151+
type: network
152+
# ...
153+
----
154+
<1> Delete the `name` value for the external load balancer, which ends in `-ext`.
155+
<2> Delete the `type` value for the external load balancer.
156+
endif::cpmso-using-aws[]
157+
158158
ifeval::["{context}" == "configuring-private-cluster"]
159159
:!post-install:
160160
endif::[]

0 commit comments

Comments
 (0)