Step 2: Navigate to Kubernetes and then click on K8s Security Groups.
Step 3: Click on the kebab menu next to the security group for which you want to view security group rules, and click Manage Rules.
Step 4: Here, you can view all your security group rules.
b. How to Create a Security Group Rule?
Step 1: On the Manage Rules page, click Create Security Group Rule.
Step 2: In the Add Security Group Rule dialog box, configure the required rule settings.
Parameter
Description
Direction
Specifies the traffic flow for the rule. Select Ingress to allow incoming traffic or Egress to allow outgoing traffic.
Protocol
Select the network protocol for the rule.
Ether Type
Specifies the IP version for the rule. Select IPv4 or IPv6.
CIDR
Enter the IP address range in CIDR notation to which the rule applies (for example, 192.168.1.0/24 or 0.0.0.0/0).
Minimum Port Range
Specifies the starting port number for the rule. Leave blank if the selected protocol does not require ports.
Maximum Port Range
Specifies the ending port number for the rule. For a single port, enter the same value in both the minimum and maximum port fields.
Description
Enter an optional description to help identify the purpose of the security group rule.
Step 3: Click Add Rule to create the security group rule.
Note: Ensure that the CIDR range, protocol, and port range are configured correctly to allow only the required network traffic while maintaining the security of your Kubernetes environment.
c. How to Delete a Security Group Rule?
Step 1: Locate the required security group, click the Kebab (⋮) menu under the Actions column, and select Manage Rules.
Step 2: On the Manage Rules page, select either the Inbound Rules or Outbound Rules tab, depending on the rule you want to delete.
Step 3: Locate the required rule, click the Kebab (⋮) menu next to the rule, and select Delete.
Step 4: In the confirmation dialog, click Delete to remove the security group rule permanently.
Note: Deleting a security group rule is permanent and cannot be undone. Ensure that the rule is no longer required before confirming the deletion.
