Changing the control plane type with CLI (v2)
Different Kubernetes cluster types are available.
You can use the CLI to specify your cluster type of choice when creating a new cluster, as well as changing the cluster type once the cluster has already been created.
In this tutorial, we show you how to change your cluster type using the Scaleway CLI (v2).
You may need certain IAM permissions to carry out some actions described on this page. This means:
Run the following command to list the viable cluster types.scw k8s cluster-type list
The output provides the details of each type, such as available stock, features and commitment:$ scw k8s cluster-type listNAME AVAILABILITY MAX NODES COMMITMENT DELAY SLAkapsule available 150 0 seconds 0kapsule-dedicated-4 available 250 30 days 99.5kapsule-dedicated-8 available 500 30 days 99.5kapsule-dedicated-16 available 500 30 days 99.5multicloud available 150 0 seconds 0multicloud-dedicated-4 available 250 30 days 99.5multicloud-dedicated-8 available 500 30 days 99.5multicloud-dedicated-16 available 500 30 days 99.5
Run the following command to know which of the clusters are available and compatible with your current type. The availability is defined by the current type, commitment and overall stock.
<cluster-id>with the ID of your current cluster.scw k8s cluster list-available-types <cluster-id>
An output like the following displays:ClusterTypes.0.Name kapsuleClusterTypes.0.Availability availableClusterTypes.0.MaxNodes 150ClusterTypes.0.CommitmentDelay 0 secondsClusterTypes.0.SLA 0ClusterTypes.0.Resiliency standardClusterTypes.0.Memory 4.0 GBClusterTypes.0.Dedicated falseClusterTypes.1.Name kapsule-dedicated-4ClusterTypes.1.Availability availableClusterTypes.1.MaxNodes 250ClusterTypes.1.CommitmentDelay 30 daysClusterTypes.1.SLA 99.5ClusterTypes.1.Resiliency high_availabilityClusterTypes.1.Memory 4.0 GBClusterTypes.1.Dedicated trueClusterTypes.2.Name kapsule-dedicated-8ClusterTypes.2.Availability availableClusterTypes.2.MaxNodes 500ClusterTypes.2.CommitmentDelay 30 daysClusterTypes.2.SLA 99.5ClusterTypes.2.Resiliency high_availabilityClusterTypes.2.Memory 8.0 GBClusterTypes.2.Dedicated trueClusterTypes.3.Name kapsule-dedicated-16ClusterTypes.3.Availability availableClusterTypes.3.MaxNodes 500ClusterTypes.3.CommitmentDelay 30 daysClusterTypes.3.SLA 99.5ClusterTypes.3.Resiliency high_availabilityClusterTypes.3.Memory 16 GBClusterTypes.3.Dedicated trueTotalCount 4
Retrieve the details of your cluster to determine the commitment period.scw k8s cluster get <cluster-id>Important:
Dedicated control plane environments come with a commitment to keep the environment for at least 30 calendar days. Keep in mind that:
- Upgrading to a higher tier cluster type restarts the 30 days of commitment
- Downgrading a cluster’s control plane is not possible during an active commitment period
- No commitment extensions are applied for downgrades after the commitment period. Once the commitment period is completed, migrating to a lower tier is possible from the console.
An output like the following displays:ID 3b5f45cf-a915-4657-aabb-1e5b5c20f8a1Type kapsuleName name-of-your-clusterStatus pool_requiredVersion 1.28.0Region fr-parOrganizationID e6af22c7-45d6-4ba7-a286-551c6d8409c5ProjectID e6af22c7-45d6-4ba7-a286-551c6d8409c5Cni ciliumDescription -ClusterURL https://3b5f45cf-a915-4657-aabb-1e5b5c20f8a1.api.k8s.fr-par.scw.cloud:6443DNSWildcard *.3b5f45cf-a915-4657-aabb-1e5b5c20f8a1.nodes.k8s.fr-par.scw.cloudCreatedAt 1 hour agoUpdatedAt 1 hour agoDashboardEnabled falseIngress noneUpgradeAvailable falseCommitmentEndsAt 1 hour ago[...]
Change the cluster type.Important:
Upgrading or downgrading causes no downtime to your workload. Your control plane might be unreachable for a maximum of two minutes during a change of offers.scw k8s cluster set-type <cluster-id> type=<cluster-type> region=<region-of-cluster>
<region-of-cluster>with their respective values.Important:
The region of your cluster cannot be changed.
If your cluster is located in a region other than
fr-par, you must specify which one in the command. Otherwise, an error will be returned.
If the operation is successful, your cluster starts updating to the new cluster type.