Skip to content

Commit c20017a

Browse files
authored
Merge pull request #102879 from openshift-cherrypick-robot/cherry-pick-89851-to-enterprise-4.17
[enterprise-4.17] OCPBUGS-45800#updating resources info
2 parents 31ca89c + 4f911b3 commit c20017a

File tree

1 file changed

+44
-43
lines changed

1 file changed

+44
-43
lines changed

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

Lines changed: 44 additions & 43 deletions
Original file line numberDiff line numberDiff line change
@@ -31,8 +31,51 @@ 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+
*** {aws-short} clusters: 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+
*** {azure-short}: Delete the following resources:
42+
** The `api-v4` rule for the public load balancer.
43+
** The `frontendIPConfiguration` parameter that is associated with the `api-v4` rule for the public load balancer.
44+
** The public IP that is specified in the `frontendIPConfiguration` parameter.
45+
46+
.. {azure-short} clusters: Configure the Ingress Controller endpoint publishing scope to `Internal`.
47+
For more information, see "Configuring the Ingress Controller endpoint publishing scope to Internal".
48+
49+
endif::cpmso-using-aws[]
50+
51+
.. Delete the
52+
ifdef::cpmso-using-aws[`api.$clustername.$yourdomain`]
53+
ifdef::post-install[`api.$clustername.$yourdomain` or]
54+
ifndef::cpmso-using-aws[`api.$clustername`]
55+
DNS entry in the public zone.
56+
57+
ifdef::cpmso-using-aws[]
58+
. Remove the external load balancers by deleting the following indicated lines in the control plane machine set custom resource:
59+
+
60+
[source,yaml]
61+
----
62+
# ...
63+
providerSpec:
64+
value:
65+
# ...
66+
loadBalancers:
67+
- name: lk4pj-ext # <1>
68+
type: network # <2>
69+
- name: lk4pj-int
70+
type: network
71+
# ...
72+
----
73+
<1> Delete the `name` value for the external load balancer, which ends in `-ext`.
74+
<2> Delete the `type` value for the external load balancer.
75+
endif::cpmso-using-aws[]
76+
3477
ifdef::post-install[]
35-
. AWS clusters: Remove the external load balancers:
78+
. {aws-short} clusters: Remove the external load balancers:
3679
+
3780
[IMPORTANT]
3881
====
@@ -113,48 +156,6 @@ providerSpec:
113156
.... Repeat this process for each of the control plane machines.
114157
endif::post-install[]
115158

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-
158159
ifeval::["{context}" == "configuring-private-cluster"]
159160
:!post-install:
160161
endif::[]

0 commit comments

Comments
 (0)