Skip to content

Commit 436e736

Browse files
authored
docs(k8s): add ubuntu version (#5826)
* docs(k8s): add ubuntu version * fix(k8s): update warning
1 parent 04d8f75 commit 436e736

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

pages/kubernetes/quickstart.mdx

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -133,9 +133,10 @@ This section outlines the settings for your cluster pools. You can configure as
133133
* 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.
134134
7. Click **Create cluster**. Your cluster is deployed, and you are taken to the cluster’s **Overview** tab.
135135
<Message type="important">
136-
Make sure you have:
137-
* An `arm64` or `amd64` server running with Ubuntu or Debian, having a public IP assigned to it.
138-
* A Scaleway [secret key](/iam/how-to/create-api-keys/).
136+
The Kosmos agent/installer supports Ubuntu 24.04 and may work on Debian based distributions.
137+
It is available for `arm64` or `amd64` server architectures
138+
139+
Bear in mind that we **do not provide support on external nodes**.
139140
</Message>
140141
<Message type="tip">
141142
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.
@@ -163,4 +164,4 @@ This section outlines the settings for your cluster pools. You can configure as
163164
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**.
164165
<Message type="important">
165166
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).
166-
</Message>
167+
</Message>

0 commit comments

Comments
 (0)