Set Up a Kubernetes Cluster

Prerequisite: Only contract administrators, owners, and users with Create Kubernetes Clusters permission can create a cluster for Public and Private Node Pools. Other user types have read-only access.

Public Node Pools

You can create a cluster using the Kubernetes Manager in DCD for Public Node Pools.

Note:

• A total of 500 node pools per cluster are supported.

• It is not possible to switch the Node pool type from public to private and vice versa.

1. In the DCD, go to Containers > Managed Kubernetes.

Containers drop-down menu

1. Select + Create Cluster.

2. Enter a Name for the cluster.

Note: Make sure to use the following naming convention for the Kubernetes cluster:

• Can be a maximum of 63 characters in length.

• Begins and ends with an alphanumeric character ([a-z0-9A-Z]).

• Must not contain spaces or any other white-space characters.

• Can contain dashes (-), underscores (_), and dots (.) in between.

1. Select the Kubernetes Version you want to run in the cluster from the drop-down list.

2. Select a Region from the drop-down list.

3. In the Node pool type field, choose Public from the drop-down list.

4. Click + Create Cluster.

Accessing the Create Cluster modal

Result: A cluster is successfully created and listed in the clusters list for Public Node Pools. The cluster can be modified and populated with node pools once its status is active.

Private Node Pools

You can create a cluster using the Kubernetes Manager in DCD for Private Node Pools. For this cluster, you have to provide a Gateway IP. It is the IP address assigned to the deployed Network Address Translation (NAT) Gateway. The IP address must be reserved in the Management > IP Management.

Note:

• When defining a private node pool, you need to provide a data center in the same location as the cluster for which you create the node pool.

• A total of 500 node pools per cluster are supported.

• It is not possible to switch the Node pool type from private to public and vice versa.

To create a cluster for Private Node Pools in Kubernetes Manager, follow these steps:

1. In the DCD, go to Menu > Containers > Managed Kubernetes.

Containers drop-down menu

1. Select + Create Cluster.

2. Enter a Name for the cluster.

Note: Make sure to use the following naming convention for the Kubernetes cluster:

• Can be a maximum of 63 characters in length.

• Begins and ends with an alphanumeric character ([a-z0-9A-Z]).

• Must not contain spaces or any other white-space characters.

• Can contain dashes (-), underscores (_), and dots (.) in between.

1. Select the Kubernetes Version you want to run in the cluster from the drop-down list.

2. In the Node pool type field, choose Private from the drop-down list.

3. Select a Region from the drop-down list.

Note: You can only create the cluster for Private Node Pools in the Virtual Data Centers (VDCs) in the same region as the cluster.

1. Select a reserved IP address from the drop-down list in Gateway IP. To do this, you need to reserve an IPv4 address assigned by IONOS Cloud. For more information, see Reserve an IPv4 Address.

2. (Optional) Define a Subnet for the private LAN. This has to be an address of a prefix length /16 in the Classless Inter-Domain Routing (CIDR) block.

Note:

• The subnet value cannot intersect with the cluster's networks for pods and services. For clusters created with:

  • Kubernetes version 1.30 and above, the networks are 100.96.0.0/12 and 100.64.0.0/18.

  • Older Kubernetes versions, the networks are 10.208.0.0/12 and 10.233.0.0/18.

• Once provisioned, the Region, Gateway IP, and Subnet values cannot be changed.

1. Click + Create Cluster.

Creating a cluster for a private node pool

Result: A cluster is successfully created and listed in the clusters list for Private Node Pools.

Note:

• To access the Kubernetes API provided by the cluster, download the kubeconfig file and use it with tools such as kubectl.

• The maintenance window starts at the time of your choosing and remains open for another four hours. All planned maintenance work will be performed within this window, however, not necessarily at the beginning.