Creating a Policy (for a Cluster Using the Container Tunnel Network Model)

Constraints

• Only clusters that use the tunnel network model support network policies. Network policies are classified into the following types:
  • Inbound rules, which are supported by all CCE cluster versions.
  • Outbound rules, which are supported only by CCE clusters in version 1.23 and later.
• Network isolation is not supported for IPv6 addresses.

Creating a Network Policy from YAML

1. Log in to the management console.
2. Click in the upper left corner of the page, select a region, and choose Security > Host Security Service.
3. In the navigation pane, choose Prevention > Container Firewalls.
4. Click Manage Policy in the Operation column of a cluster using the container tunnel network model.
5. Click Create from YAML above the policy list.
6. On the YAML creation page, enter content or click Import.

   An example of a network policy created from YAML is as follows:

   apiVersion: networking.k8s.io/v1
   kind: NetworkPolicy
   metadata:
     name: test-network-policy
     namespace: default
   spec:
     podSelector:                  # The rule takes effect for pods with the role=db label.
       matchLabels:
         role: db
     policyTypes:
       - Ingress
       - Egress
     ingress:                      # Ingress rule
       - from:
           - namespaceSelector: # Only namespaces with project=myproject can be accessed.
               matchLabels:
                 project: myproject
           - podSelector:              # Only the traffic from the pods with the role=frontend label is allowed.
               matchLabels:
                 role: frontend
         ports                       # Only TCP can be used to access port 6379.
           - protocol: TCP
             port: 6379
     egress:                         # Egress rule
       - to:
           - ipBlock:                #Only the 10.0.0.0/24 network segment of the destination object can be accessed.
               cidr: 10.0.0.0/24
         ports:                      # Only TCP can be used to access port 6379 of the destination object.
           - protocol: TCP
             port: 6379
   

7. Click OK.

Creating a Network Policy on the GUI

1. Log in to the management console.
2. In the navigation pane, choose Prevention > Container Firewalls.
3. Click Manage Policy in the Operation column of a cluster using the container tunnel network model.
4. Click Create Network Policy above the network policy list.
   • Policy Name: Enter a network policy name.
   • Namespace: Select a namespace for the network policy.
   • Selector: Enter a key and a value to set the pod to be associated, and click Add. You can also click Reference Workload Label to reference the label of an existing workload. If this parameter is not specified, all pods in the namespace are associated by default.
   • Inbound rule: Click Add Rule in the Inbound Rules area. For more information, see Table 1.

     Table 1 Adding an inbound rule

     Parameter	Description
     Protocol & Port	Enter the inbound protocol type and port number of the pods to be associated. Currently, TCP and UDP are supported. If this parameter is not specified, all access traffic is allowed.
     Source Namespace	Select a namespace whose objects can be accessed. If this parameter is not specified, access to the objects that belong to the same namespace as the current policy is allowed.
     Source Pod Label	Select a label. Pods with this label can be accessed. If this parameter is not specified, all pods in the namespace can be accessed.

   • Outbound rule: Click Add Rule in the Outbound Rules area. For more information, see Table 2.

     Table 2 Adding an outbound rule

     Parameter	Description
     Protocol & Port	Enter the port and protocol of destination objects. If this parameter is not specified, access is not limited.
     Destination CIDR Block	Configure CIDR blocks. This parameter allows requests to be routed to a specified CIDR block (and not to the exception CIDR blocks). Separate the destination and exception CIDR blocks by vertical bars (|), and separate multiple exception CIDR blocks by commas (,). For example, 172.17.0.0/16|172.17.1.0/24,172.17.2.0/24 indicates that 172.17.0.0/16 is accessible, but not for 172.17.1.0/24 or 172.17.2.0/24.
     Destination Namespace	Namespace where the destination object is located. If not specified, the object belongs to the same namespace as the current policy.
     Destination Pod Label	Select a label. Pods with this label can be accessed. If this parameter is not specified, all pods in the namespace can be accessed.

5. Click OK.

Related Operations

Synchronizing CCE network policies

Network policies created in CCE can be synchronized to HSS.

1. Click Synchronize above the network policy list.
2. Check the value of Last synchronized. If it changes to the completion time of the latest synchronization task, the synchronization is complete.