Skip to content

docs(k8s): add warning to documentation #5725

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.

Sign up for GitHub

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
merged 2 commits into from
Oct 29, 2025
Merged

docs(k8s): add warning to documentation #5725

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
46f6fa3
docs(k8s): add warning to documentation
bene2k1 Oct 28, 2025
5bf5081
fix(k8s): close message
bene2k1 Oct 29, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 9 additions & 3 deletions pages/kubernetes/how-to/upgrade-kapsule-new-node-image-system.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ title: How to upgrade a Kapsule cluster to the new node image system
description: Learn how to upgrade a Kapsule cluster to the new node image system.
tags: kubernetes kapsule node image
dates:
validation: 2025-09-04
validation: 2025-10-28
posted: 2025-09-04
categories:
- containers
Expand All @@ -17,7 +17,7 @@ Upgrades will also be faster, as nodes will be replaced instead of rebooted.

## Technical specifications of the upgrade process

* **Node replacement**: During upgrade, nodes will be replaced with new ones, which may have implications for data stored locally on nodes (e.g., `hostPath`). Data stored in persistent volumes (PV) will not be affected.
* **Node replacement**: During upgrade, nodes will be replaced with new ones, **any local data will be lost**. Data stored in Persistent Volumes (PV) will not be affected.
* **New IP addresses**: The new replacement nodes will have new IP addresses (both public and private), which could impact IP filtering configurations.
* **GPU pool upgrade**: The upgrade of GPU pools may result in a partial downtime due to a limitation in the GPU operator, which cannot handle mixed Ubuntu versions (22.04 vs 24.04). The operator will install incorrect drivers on new nodes until the upgrade is complete, after which it will recover automatically.

Expand All @@ -30,6 +30,12 @@ Upgrades will also be faster, as nodes will be replaced instead of rebooted.

You can upgrade your Scaleway Kubernetes Kapsule cluster to the new image system using either the console or the CLI.

<Message type="important">
During the upgrade process, all cluster nodes will be replaced with new ones.
Any data stored locally on the nodes (for example, using `hostPath`) will be **permanently lost**.
Data stored in **Persistent Volumes (PVs)** will **not** be affected.
</Message>

### Console upgrade

1. Navigate to **Kubernetes** under the **Containers** section of the [Scaleway console](https://console.scaleway.com/) side menu. The Kubernetes dashboard displays.
Expand All @@ -48,5 +54,5 @@ Example of commands:
```
* Migrate a specific pool of a cluster to new images:
```
scw k8s pool migrate-to-new-images cluster-id=11111111-1111-1111-1111-111111111111 pools.0=22222222-2222-2222-2222-222222222222
scw k8s pool migrate-to-new-images cluster-id=11111111-1111-1111-1111-111111111111 pools-ids.0=22222222-2222-2222-2222-222222222222
```