-
Notifications
You must be signed in to change notification settings - Fork 258
docs(ins): add warning for kapsule nodes #5166
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
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
58ac1b3
docs(ins): add warning for kapsule nodes
bene2k1 99dc6b3
Apply suggestions from code review
bene2k1 b1ac7d8
feat(k8s): add delete pool
bene2k1 c824ef4
Apply suggestions from code review
bene2k1 d58edaa
feat(k8s): update doc
bene2k1 fc820d3
docs(k8s): update
bene2k1 c3a0292
feat(k8s): update navigation
bene2k1 90c55b6
Apply suggestions from code review
bene2k1 20aaa10
Apply suggestions from code review
bene2k1 d015d80
feat(k8s): update wording
bene2k1 4d1245d
Apply suggestions from code review
bene2k1 2752705
feat(k8s): add links to cli
bene2k1 e9f21c0
feat(k8s): update wording
bene2k1 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,100 @@ | ||
| --- | ||
| meta: | ||
| title: How to manage Kubernetes Kapsule node pools | ||
| description: Learn how to manage Kubernetes Kapsule node pools from the Scaleway console. | ||
bene2k1 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| content: | ||
| h1: How to manage Kubernetes node pools | ||
| paragraph: Learn how to manage Kubernetes Kapsule node pools from the Scaleway console. | ||
| tags: kubernetes kapsule kosmos | ||
| dates: | ||
| validation: 2025-06-23 | ||
| posted: 2025-06-23 | ||
| categories: | ||
| - containers | ||
| --- | ||
|
|
||
| This documentation provides step-by-step instructions on how to manage Kubernetes Kapsule node pools using the Scaleway console. | ||
|
|
||
| <Macro id="requirements" /> | ||
|
|
||
| - A Scaleway account logged into the [console](https://console.scaleway.com) | ||
| - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization | ||
| - Created a [Kubernetes Kapsule cluster](/kubernetes/how-to/create-cluster/) | ||
|
|
||
| ## How to create a new Kubernetes Kapsule node pool | ||
|
|
||
| <Message type="tip"> | ||
| Kubernetes Kapsule supports using both **fully isolated** and **controlled isolation** node pools within the same cluster. [Learn more.](/kubernetes/reference-content/secure-cluster-with-private-network/#what-is-the-difference-between-controlled-isolation-and-full-isolation) | ||
| </Message> | ||
|
|
||
| 1. Navigate to **Kubernetes** under the **Containers** section of the [Scaleway console](https://console.scaleway.com/) side menu. The Kubernetes dashboard displays. | ||
| 2. Click the Kapsule cluster name you want to manage. The cluster information page displays. | ||
| 3. Click the **Pools** tab to display the pool configuration of the cluster. | ||
| 4. Click **Add pool** to launch the pool creation wizard. | ||
| 5. Configure the pool: | ||
| - Choose the **Availability Zone** for the pool. | ||
| - Choose the commercial type of Instance for the pool. | ||
| - Configure the system volume. | ||
| - Configure pool options. | ||
| - Enter the pool's details. | ||
| 6. Click **Add pool**. The pool gets added to your basket. Repeat the steps above to configure additional pools. | ||
| 7. Click **Review** once you have configured the desired pools. A summary of your configuration displays. | ||
| 8. Verify your configuration and click **Submit** to add the pool(s) to your Kapsule cluster. | ||
|
|
||
| <Message type="note"> | ||
| Alternatively, you can use the Scaleway CLI to [create node pools](https://cli.scaleway.com/k8s/#create-a-new-pool-in-a-cluster). | ||
| </Message> | ||
|
|
||
| ## How to edit an existing Kubernetes Kapsule node pool | ||
|
|
||
| 1. Navigate to **Kubernetes** under the **Containers** section of the [Scaleway console](https://console.scaleway.com/) side menu. The Kubernetes dashboard displays. | ||
| 2. Click the Kapsule cluster name you want to manage. The cluster information page displays. | ||
| 3. Click the **Pools** tab to display the pool configuration of the cluster. | ||
| 4. Click <Icon name="more" /> > **Edit** next to the node pool you want to edit. | ||
| 5. Configure the pool: | ||
| - Update pool tags | ||
| - Configure autoscaling | ||
| - Enable or disable the [autoheal feature](/kubernetes/reference-content/using-kapsule-autoheal-feature/) | ||
| 6. Click **Update pool** to update the pool configuration. | ||
|
|
||
| <Message type="note"> | ||
| Alternatively, you can use the Scaleway CLI to [update a node pool](https://cli.scaleway.com/k8s/#update-a-pool-in-a-cluster). | ||
| </Message> | ||
|
|
||
| ## How to migrate existing workloads to a new Kubernets Kapsule node pool | ||
|
|
||
| <Message type="important"> | ||
| Always ensure that your **data is backed up** before performing any operations that could affect it. | ||
| </Message> | ||
|
|
||
| 1. Create the new node pool with the desired configuration either [from the console](#how-to-create-a-new-kubernetes-kapsule-node-pool) or by using the Scaleway CLI tool `scw`. | ||
| <Message type="tip"> | ||
| Ensure that the new node pool is properly labeled if necessary. | ||
| </Message> | ||
| 2. Run `kubectl get nodes` to check that the new nodes are in a `Ready` state. | ||
| 3. Cordon the nodes in the old node pool to prevent new pods from being scheduled there. For each node, run: `kubectl cordon <node-name>` | ||
bene2k1 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| <Message type="tip"> | ||
| You can use a selector on the pool name label to cordon or drain multiple nodes at the same time if your app allows it (ex. `kubectl cordon -l k8s.scaleway.com/pool-name=mypoolname`) | ||
| </Message> | ||
| 4. Drain the nodes to evict the pods gracefully. | ||
| - For each node, run: `kubectl drain <node-name> --ignore-daemonsets --delete-emptydir-data` | ||
| - The `--ignore-daemonsets` flag is used because daemon sets manage pods across all nodes and will automatically reschedule them. | ||
| - The `--delete-emptydir-data` flag is necessary if your pods use emptyDir volumes, but use this option carefully as it will delete the data stored in these volumes. | ||
| - Refer to the [official Kubernetes documentation](https://kubernetes.io/docs/tasks/administer-cluster/safely-drain-node/) for further information. | ||
| 5. Run `kubectl get pods -o wide` after draining, to verify that the pods have been rescheduled to the new node pool. | ||
| 6. [Delete the old node pool](#how-to-delete-an-existing-kubernetes-kapsule-node-pool) once you confirm that all workloads are running smoothly on the new node pool. | ||
|
|
||
bene2k1 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| ## How to delete an existing Kubernetes Kapsule node pool | ||
|
|
||
| 1. Navigate to **Kubernetes** under the **Containers** section of the [Scaleway console](https://console.scaleway.com/) side menu. The Kubernetes dashboard displays. | ||
| 2. Click the Kapsule cluster name you want to manage. The cluster information page displays. | ||
| 3. Click the **Pools** tab to display the pool configuration of the cluster. | ||
| 4. Click <Icon name="more" /> > **Delete** next to the node pool you want to delete. | ||
| 5. Click **Delete pool** in the pop-up to confirm deletion of the pool. | ||
| <Message type="important"> | ||
| This action will permanently destroy your pool and all its data. | ||
| </Message> | ||
|
|
||
| <Message type="note"> | ||
| Alternatively, you can use the Scaleway CLI to [delete a node pool](https://cli.scaleway.com/k8s/#delete-a-pool-in-a-cluster). | ||
| </Message> | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.