10.5.2. Configuring Amazon Web Services features for control plane machines

Procedure

1. Log in to the AWS console as a user with administrator privileges.

2. 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.

3. Delete the api.<cluster_name>.<domain_name> DNS entry in the public zone.

   where <cluster_name> is the name of the cluster and <domain_name> is the base domain for the cluster.

4. To remove the external load balancers, log in to the OpenShift CLI (oc) as a user with administrator privileges.

5. Edit the ControlPlaneMachineSet CR by running the following command:

   $ oc edit controlplanemachineset.machine.openshift.io cluster \
     -n openshift-machine-api

6. Remove the external load balancers by deleting the corresponding lines in the control plane machine set custom resource (CR).

   In the spec.template.spec.providerSpec.value.loadBalancers section of the CR, the name value for the external load balancer ends in -ext. Delete the line with the external load balancer name value and the line with the external load balancer type value that accompanies it.

   apiVersion: machine.openshift.io/v1
   kind: ControlPlaneMachineSet
   metadata:
     name: cluster
     namespace: openshift-machine-api
   spec:
   # ...
     template:
   # ...
         spec:
           providerSpec:
             value:
               loadBalancers:
               - name: <cluster_id>-ext
                 type: network
               - name: <cluster_id>-int
                 type: network
   # ...

7. Save your changes and exit the object specification.

   When you save an update to the control plane machine set, the Control Plane Machine Set Operator updates the control plane machines according to your configured update strategy. For more information, see "Updating the control plane configuration".