You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: pages/kubernetes/reference-content/security-group-management.mdx
+43-5Lines changed: 43 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,9 +13,47 @@ categories:
13
13
- kubernetes
14
14
---
15
15
16
-
Scaleway Kubernetes Kapsule and Kosmos provide managed Kubernetes services that simplify the deployment and management of containerized applications. As part of the security configuration for these services, Scaleway allows users to manage security groups for Kapsule pools to control network traffic to and from cluster nodes. This document outlines the process for managing security groups when creating and configuring pools in Scaleway Kubernetes Kapsule.
17
-
Security Group Management for Kapsule Pools
18
-
When creating a Kapsule pool, you can specify a security group ID to associate an existing security group with the pool. This allows for customized network traffic rules tailored to your specific requirements.
16
+
Scaleway Kubernetes Kapsule and Kosmos provide managed Kubernetes services that simplify the deployment and management of containerized applications.
17
+
As part of the security configuration for these services, Scaleway allows users to manage security groups for Kapsule pools to control network traffic to and from cluster nodes.
18
+
This document outlines the process for managing security groups when creating and configuring pools in Scaleway Kubernetes Kapsule.
19
19
20
-
If no security group ID is provided during pool creation, Scaleway assigns a default preconfigured security group named **Kapsule default security group**. This default security group is shared across all Kapsule pools within the same availability zone.
21
-
Key Changes
20
+
<Messagetype="note">
21
+
Previously, Scaleway created a separate security group for each zone where a cluster had at least one pool. This approach has been replaced with the option to use either a user-specified security group or the shared default security group.
22
+
</Message>
23
+
24
+
## Security group management for Kapsule pools
25
+
26
+
When creating a pool using the CLI or API, you can specify a security group ID to associate an existing security group with the pool. This allows for customized network traffic rules tailored to your specific requirements.
27
+
28
+
Run the following syntax to create a new pool using the CLI:
29
+
```
30
+
scw k8s pool create cluster-id=11111111-1111-1111-1111-111111111111 name=bar node-type=DEV1-XL size=2 security-group-id11111111-1111-1111-1111-111111111111
31
+
```
32
+
<Messagetype="note">
33
+
Replace `11111111-1111-1111-1111-111111111111` with the UUID of your cluster and security group.
34
+
</Message>
35
+
36
+
For more information how to create a pool using the API, refer to the [Kubernetes API documentation](https://www.scaleway.com/en/developers/api/kubernetes/#path-pools-create-a-new-pool-in-a-cluster).
37
+
38
+
If no security group ID is provided during pool creation, Scaleway assigns a default preconfigured security group named **Kapsule default security group**.
39
+
This default security group is shared across all Kapsule pools within the same availability zone.
40
+
41
+
### Verify security group configuration
42
+
43
+
After creating the pool, verify that the correct security group is applied by checking the pool details in the Scaleway console or using the CLI:
44
+
45
+
```bash
46
+
scw k8s pool get <pool-id>
47
+
```
48
+
49
+
Ensure that the security group rules align with your application's networking needs and cluster communication requirements.
50
+
51
+
52
+
## Modify security group rules (Optional):
53
+
54
+
To update the rules of an existing security group, navigate to the Instances section in the Scaleway console.
55
+
Select the security group (either the custom one or the Kapsule default security group) and [modify the inbound/outbound rules](/instances/how-to/use-security-groups/#how-to-edit-a-security-group) as needed.
56
+
57
+
<Messagetype="important">
58
+
Changes to the Kapsule default security group will affect all pools in the same zone that use this default group.
0 commit comments