When the Cloud Native Network 2.0 model is used, pods use VPC ENIs or sub-ENIs for networking. You can directly bind security groups and EIPs to pods. CCE provides a custom resource object named SecurityGroup for you to associate security groups with pods in CCE. You can customize workloads with specific security isolation requirements using SecurityGroups.
Notes and Constraints
- This function is supported for CCE Turbo clusters of v1.19 and later. Upgrade your CCE Turbo clusters if their versions are earlier than v1.19.
- A workload can be bound to a maximum of five security groups.
Using the Console
- In the navigation pane of the CCE console, choose Resource Management > Network.
- On the SecurityGroup tab page, select the target cluster in the upper right corner and click Create.
- Set the parameters as described in Table 1.
Table 1 Configuration parameters
Enter a SecurityGroup name.
Enter 4 to 63 characters. The value must start with a lowercase letter and cannot end with a hyphen (-). Only lowercase letters, digits, and hyphens (-) are allowed.
Select a cluster.
Select a namespace. If the namespace is not created, click Create Namespace.
Select a workload.
The selected security group will be bound to the ENI or supplementary ENI of the selected workload. A maximum of five security groups can be selected from the drop-down list. You must select one or multiple security groups to create a SecurityGroup.
If no security group has not been created, click Create Security Group. After the security group is created, click the refresh button.NOTICE:
- A maximum of 5 security groups can be selected.
- Hover the cursor on the security group name, and you can view details about the security group.
- After setting the parameters, click Create.
After the SecurityGroup is created, the system automatically returns to the SecurityGroup list page. You can see that the newly added SecurityGroup is in the list.
- Use kubectl to connect to the cluster. For details, see Connecting to a Cluster Using kubectl.
- Create a description file named securitygroup-demo.yaml.
For example, create the following SecurityGroup to bind all nginx workloads with two security groups 64566556-bd6f-48fb-b2c6-df8f44617953 and 5451f1b0-bd6f-48fb-b2c6-df8f44617953 that have been created in advance. An example is as follows:
apiVersion: crd.yangtse.cni/v1 kind: SecurityGroup metadata: name: demo namespace: default spec: podSelector: matchLabels: app: nginx securityGroups: - id: 64566556-bd6f-48fb-b2c6-df8f44617953 - id: 5451f1b0-bd6f-48fb-b2c6-df8f44617953Table 2 describes the parameters in the YAML file.
Table 2 Description
API version. The value is crd.yangtse.cni/v1.
Type of the object to be created.
Metadata definition of the resource object.
Name of the SecurityGroup.
Name of the namespace.
Detailed description of the SecurityGroup.
Used to define the workload to be associated with security groups in the SecurityGroup.
Security group ID.
- Run the following command to create the SecurityGroup:
kubectl create -f securitygroup-demo.yaml
If the following information is displayed, the SecurityGroup is being created.
- Run the following command to view the SecurityGroup:
kubectl get sg
If the name of the created SecurityGroup is demo in the command output, the SecurityGroup is created successfully.
NAME POD-SELECTOR AGE all-no map[matchLabels:map[app:nginx]] 4h1m s001test map[matchLabels:map[app:nginx]] 19m demo map[matchLabels:map[app:nginx]] 2m9s
Viewing the YAML file
Was this page helpful?Provide feedback
For any further questions, feel free to contact us through the chatbot.Chatbot