Skip to content

docs(k8s): add ubuntu version #5826

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
Nov 18, 2025
Merged

docs(k8s): add ubuntu version #5826

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b7f9316
docs(k8s): add ubuntu version
bene2k1 Nov 17, 2025
193ce84
fix(k8s): update warning
bene2k1 Nov 17, 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
4 changes: 2 additions & 2 deletions pages/kubernetes/quickstart.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -134,7 +134,7 @@ This section outlines the settings for your cluster pools. You can configure as
7. Click **Create cluster**. Your cluster is deployed, and you are taken to the cluster’s **Overview** tab.
<Message type="important">
Make sure you have:
* An `arm64` or `amd64` server running with Ubuntu or Debian, having a public IP assigned to it.
* An `arm64` or `amd64` server running on Ubuntu 24.04 or Debian, having a public IP assigned to it.
* A Scaleway [secret key](/iam/how-to/create-api-keys/).
</Message>
<Message type="tip">
Expand Down Expand Up @@ -163,4 +163,4 @@ This section outlines the settings for your cluster pools. You can configure as
4. Type **DELETE** to confirm the deletion of your cluster. Tick the checkbox to automatically delete all volumes (including those with volume type “retain”) and Load Balancers whose names start with the cluster ID. Validate your choice by clicking **Delete cluster**.
<Message type="important">
Deleting your cluster will permanently destroy your cluster and all its associated pools and Instances. External compute resources cannot be destroyed automatically and will remain active until destroyed at the concerned cloud service provider (CSP).
</Message>
</Message>