You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/private-clusters-setting-api-private.adoc
+42-42Lines changed: 42 additions & 42 deletions
Original file line number
Diff line number
Diff line change
@@ -31,48 +31,6 @@ you can reconfigure the API server to use only the private zone.
31
31
32
32
.Procedure
33
33
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.
. 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
-
76
34
ifdef::post-install[]
77
35
. AWS clusters: Remove the external load balancers:
78
36
+
@@ -155,6 +113,48 @@ providerSpec:
155
113
.... Repeat this process for each of the control plane machines.
156
114
endif::post-install[]
157
115
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.
0 commit comments