Skip to content
Merged
Changes from all commits
Commits
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
9 changes: 5 additions & 4 deletions pages/kubernetes/quickstart.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -133,9 +133,10 @@ This section outlines the settings for your cluster pools. You can configure as
* The configuration for your **pool options**, including the number of nodes and whether to enable autoscale. You can also choose whether to enable autoheal and whether to link the cluster to a placement group. Alternatively, you can leave these options at default values.
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.
* A Scaleway [secret key](/iam/how-to/create-api-keys/).
The Kosmos agent/installer supports Ubuntu 24.04 and may work on Debian based distributions.
It is available for `arm64` or `amd64` server architectures

Bear in mind that we **do not provide support on external nodes**.
</Message>
<Message type="tip">
For more information about adding external nodes to your Kosmos cluster, refer to our dedicated [How to manage a Kosmos cluster](/kubernetes/how-to/edit-kosmos-cluster/) documentation.
Expand Down Expand Up @@ -163,4 +164,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>