When you create a Container Service for Kubernetes (ACK) cluster, the system automatically creates an internal-facing Server Load Balancer (SLB) instance for the API server of the cluster. The SLB instance serves as the internal endpoint of the API server. If you require fine-grained access control over the API server, you can configure network access control lists (ACLs) for the listener that listens on port 6443. The network ACLs are used as whitelists or blacklists for the API server. This topic describes how to control access to the API server by configuring a listener for the internal-facing SLB instance of the API server.
- Log on to the ACK console.
- In the left-side navigation pane of the ACK console, click Clusters.
- On the Clusters page, find the cluster that you want to manage and click the name of the cluster or click Details in the Actions column. The details page of the cluster appears.
- On the Cluster Information page, click the Basic Information tab.
- On the Basic Information tab, find API Server Internal Endpoint in the Cluster Information section. Then, click Set access control.
- You are redirected to the Access Control Settings panel in the SLB console. Turn on Enable Access Control, set Access Control Method to Whitelist or Blacklist, and then select the required
Before you enable access control, you must create a network ACL. For more information about how to create a network ACL, see Create an access control list. For more information about how to enable access control, see Enable access control.Notice
- If you set a whitelist, you must add the CIDR block 100.104.0.0/16 of the ACK cluster and the CIDR block of the vSwitch to the whitelist. The vSwitch is used by the master node on which the API server runs.
- If you set a blacklist, you must not add the CIDR block 100.104.0.0/16 of the ACK cluster or the CIDR block of the vSwitch to the blacklist. The vSwitch is used by the master node on which the API server runs.
- Click OK.