-
Notifications
You must be signed in to change notification settings - Fork 225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DRAFT: feat(k8s): add acl docs #3460
base: main
Are you sure you want to change the base?
Conversation
paragraph: Learn how to manage allowed IP addresses for your Kubernetes Kapsule and Kosmos clusters. Configure access restrictions with our step-by-step guide. | ||
tags: kubernetes kapsule kosmos | ||
dates: | ||
validation: 2024-11-05 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
validation: 2024-11-05 | |
validation: 2024-12-16 |
tags: kubernetes kapsule kosmos | ||
dates: | ||
validation: 2024-11-05 | ||
posted: 2024-11-05 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
posted: 2024-11-05 | |
posted: 2024-12-16 |
Restricting IPs on Kubernetes Kapsule or Kosmos clusters enhances security by limiting access to only trusted sources, thereby reducing the risk of unauthorized access and potential attacks. | ||
This control ensures that only specific IP addresses or networks can interact with your clusters, providing an additional layer of protection. | ||
The default entry `0.0.0.0/0` enables any host to establish a connection. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Restricting IPs on Kubernetes Kapsule or Kosmos clusters enhances security by limiting access to only trusted sources, thereby reducing the risk of unauthorized access and potential attacks. | |
This control ensures that only specific IP addresses or networks can interact with your clusters, providing an additional layer of protection. | |
The default entry `0.0.0.0/0` enables any host to establish a connection. | |
Restricting IPs on Kubernetes Kapsule or Kosmos clusters enhances security by limiting access to only trusted sources. Since only IP addresses and networks specified by you can interact with your clusters, you reduce the risk of unauthorized access and potential attacks. | |
The default entry `0.0.0.0/0` enables any host to establish a connection. |
|
||
<Macro id="requirements" /> | ||
|
||
- Scaleway account logged into the [Scaleway console](https://console.scaleway.com) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Scaleway account logged into the [Scaleway console](https://console.scaleway.com) | |
- A Scaleway account logged into the [Scaleway console](https://console.scaleway.com) |
|
||
## How to add an IP address | ||
|
||
1. Click **Kubernetes** in the **Containers** section of the [Scaleway console](https://console.scaleway.com). The **Kubernetes Kapsule dashboard** appears. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1. Click **Kubernetes** in the **Containers** section of the [Scaleway console](https://console.scaleway.com). The **Kubernetes Kapsule dashboard** appears. | |
1. Click **Kubernetes** in the **Containers** section of the [Scaleway console](https://console.scaleway.com). The **Kubernetes dashboard** appears. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're specifying Kubernetes Kapsule here, but the requirements say that users can do this either on a Kapsule or Kosmos cluster. We must either remove the Kapsule mention here or state that the settings we show on this page are specifically for Kapsule, no?
1. Click **Kubernetes** in the **Containers** section of the [Scaleway console](https://console.scaleway.com). The **Kubernetes Kapsule dashboard** appears. | ||
2. Select the cluster you wish to configure. The **Cluster information** page opens. | ||
3. Click the **Network** tab to display your cluster's network information. Your access control list appears in the **Allowed IPs for control plane** section. | ||
4. Click **Add allowed IP**. Enter the IP address or IP block in [CIDR notation](/network/ipam/concepts/#cidr-notation) (e.g., `198.51.100.135/32` for a single IP, `198.51.100.0/24` for an IP block) and click **Add IPs**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
4. Click **Add allowed IP**. Enter the IP address or IP block in [CIDR notation](/network/ipam/concepts/#cidr-notation) (e.g., `198.51.100.135/32` for a single IP, `198.51.100.0/24` for an IP block) and click **Add IPs**. | |
4. Click **Add allowed IP**. Enter the IP address or IP block in [CIDR notation](/network/ipam/concepts/#cidr-notation) (e.g., `198.51.100.135/32` for a single IP, `198.51.100.0/24` for an IP block), then click **Add IP(s)**. |
|
||
## How to delete an IP address | ||
|
||
1. Click **Kubernetes** in the **Containers** section of the [Scaleway console](https://console.scaleway.com). The **Kubernetes Kapsule dashboard** appears. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Check if Kapsule mention should be here.
Your checklist for this pull request
Description
Please describe what you added or changed.