Configuring a Blocklist/Trustlist Access Policy for a LoadBalancer Ingress

Prerequisites

• A CCE standard or Turbo cluster is available, and the cluster version meets the following requirements:
  • v1.23: v1.23.12-r0 or later
  • v1.25: v1.25.7-r0 or later
  • v1.27: v1.27.4-r0 or later
  • v1.28: v1.28.2-r0 or later
  • Other clusters of later versions
• An IP address group has been created on the ELB console.

Notes and Constraints

• After a blocklist/trustlist access policy is configured, if you delete the blocklist/trustlist access policy configuration on the CCE console or delete the target annotation from the YAML file, the configuration on the ELB will be retained.
• If multiple ingresses share the same external port on a load balancer, you are advised to use the same blocklist/trustlist configuration for these ingresses. Otherwise, the configuration of the first created ingress will take precedence. For details, see Configuring Multiple Ingresses to Use the Same External ELB Port.

Using the CCE Console to Configure a Blocklist/Trustlist Access Policy

1. Log in to the CCE console and click the cluster name to access the cluster console.
2. Choose Services & Ingresses in the navigation pane, click the Ingresses tab, and click Create Ingress in the upper right corner.
3. Configure ingress parameters.
   Note

   This example explains only key parameters for configuring blocklist/trustlist access policies. You can configure other parameters as required. For details, see Creating a LoadBalancer Ingress on the Console.

   Table 1 Key parameters

   Parameter	Description	Example
   Name	Enter an ingress name.	ingress-test
   Load Balancer	Select a load balancer to be associated with the ingress or automatically create a load balancer. A load balancer can be dedicated or shared.	Dedicated
   Listener	External Protocol: HTTP and HTTPS are available. External Port: specifies the port of the load balancer listener. Access Control Inherit ELB Configurations: CCE does not modify the existing access control configurations on the ELB console. Allow all IP addresses: No access control is configured. Trustlist: Only the selected IP address group can access the load balancer. Blocklist: The selected IP address group cannot access the load balancer. NOTE: For clusters of v1.25.16-r10, v1.27.16-r10, v1.28.15-r0, v1.29.10-r0, v1.30.6-r0, v1.31.1-r0, or later, when using a dedicated load balancer, you can select a maximum of five IP address groups at a time for access control.	External Protocol: HTTP External Port: 80 Advanced Options Access Control: Blocklist
   Forwarding Policy	Domain Name: Enter an actual domain name to be accessed. If it is left blank, the ingress can be accessed through the IP address. Ensure that the domain name has been registered and licensed. Once a forwarding policy is configured with a domain name specified, you must use the domain name for access. Path Matching Rule: Select Prefix match, Exact match, or RegEx match. Path: Enter the path provided by a backend application for external access. The path added must be valid in the backend application, or the forwarding cannot take effect. Destination Service: Select an existing Service. Only Services that meet the requirements are automatically displayed in the Service list. Destination Service Port: Select the access port of the destination Service.	Domain Name: You do not need to configure this parameter. Path Matching Rule: Prefix match Path: / Destination Service: nginx Destination Service Port: 80

4. Click OK.

Using kubectl to Configure a Blocklist/Trustlist Access Policy

1. Use kubectl to access the cluster. For details, see Accessing a Cluster Using kubectl.
2. Create a YAML file named ingress-test.yaml. The file name can be customized.

   vi ingress-test.yaml
   
   

   An example YAML file of an ingress created using an existing load balancer is as follows:

   apiVersion: networking.k8s.io/v1
   kind: Ingress 
   metadata: 
     name: ingress-test
     annotations: 
       kubernetes.io/elb.id: <your_elb_id>                    # Load balancer ID. Replace it with the actual value.
       kubernetes.io/elb.class: performance                   # Load balancer type
       kubernetes.io/elb.port: '80'                           # External port of the load balancer listener
       kubernetes.io/elb.acl-id: <your_acl_id>               # ID of an IP address group for accessing a load balancer
       kubernetes.io/elb.acl-status: 'on'                    # Enable access control.
       kubernetes.io/elb.acl-type: 'white'                   # Trustlist for access control
   spec:
     rules: 
     - host: ''
       http: 
         paths: 
         - path: '/'
           backend: 
             service:
               name: <your_service_name>  # Replace it with the name of your target Service.
               port: 
                 number: 80             # Replace 80 with the port number of your target Service.
           property:
             ingress.beta.kubernetes.io/url-match-mode: STARTS_WITH
           pathType: ImplementationSpecific
     ingressClassName: cce      
   
   

   Table 2 Annotations for ELB access control

   Parameter	Type	Description
   kubernetes.io/elb.acl-id	String	If this parameter is not specified, CCE does not modify access control on the ELB. If this parameter is left empty, all IP addresses are allowed to access the load balancer. If this parameter is set to the IP address group ID of the load balancer, access control is enabled and you need to configure an IP address blocklist or trustlist for the load balancer. Additionally, you need to configure both kubernetes.io/elb.acl-status and kubernetes.io/elb.acl-type. NOTE: For clusters of v1.25.16-r10, v1.27.16-r10, v1.28.15-r0, v1.29.10-r0, v1.30.6-r0, v1.31.1-r0, or later, when using a dedicated load balancer, you can select a maximum of five IP address groups at a time, separated by commas (,). How to obtain: Log in to the console. In the Service List, choose Networking > Elastic Load Balance. On the Network Console, choose Elastic Load Balance > IP Address Groups and copy the ID of the target IP address group.
   kubernetes.io/elb.acl-status	String	This parameter is mandatory when you configure an IP address blocklist or trustlist for a load balancer. Options: on or true: Access control is enabled. off or false: Access control is disabled.
   kubernetes.io/elb.acl-type	String	This parameter is mandatory when you configure an IP address blocklist or trustlist for a load balancer. Options: black: indicates a blocklist. The selected IP address group cannot access the load balancer. white: indicates a trustlist. Only the selected IP address group can access the load balancer.

3. Create an ingress.

   kubectl create -f ingress-test.yaml
   
   

   If information similar to the following is displayed, the ingress has been created:

   ingress/ingress-test created
   
   

4. Check the created ingress.

   kubectl get ingress
   
   

   If information similar to the following is displayed, the ingress has been created:

   NAME          CLASS    HOSTS     ADDRESS          PORTS   AGE
   ingress-test  cce      *         121.**.**.**     80      10s