Deckhouse Kubernetes Platform on VMware Cloud Director

1
Selecting infrastructure
2
Installation information
3
Preparing environment
4
Installation
5
Getting access to the cluster
6
What can I do next?

Installation of Deckhouse Kubernetes Platform on VMware Cloud Director is only possible in the Enterprise Edition. See information about commercial editions.

Before starting the installation, ensure you have the cloud provider quotas required to deploy your cluster.

To use ContainerdV2 as the container runtime on cluster nodes, the operating systems on virtual machines must meet the following requirements:

  • Linux kernel version 5.8 or newer.
  • CgroupsV2 support.
  • Systemd version 244 or newer.
  • erofs kernel module support.

For more information, see the documentation.

Starting with version 1.74, the Deckhouse Kubernetes Platform has a module integrity control mechanism that protects modules from being replaced or modified. This mechanism is enabled automatically when the operating system on the nodes where Deckhouse is installed supports the erofs kernel module. If this kernel module is not present, Deckhouse will continue to operate without the module integrity control mechanism, but an alert will be displayed indicating that this functionality is not working.

The cloud-init package must be installed on the VMs. After the virtual machine is started, the following services associated with this package must be started:

  • cloud-config.service;
  • cloud-final.service;
  • cloud-init.service.

The provider supports working with only one disk in the virtual machine template. Make sure the template contains only one disk.

The provider is confirmed to work with Ubuntu 22.04-based virtual machine templates only.

To start working with the provider, you have to create a tenant with the resources listed in the documentation.

Once the tenant has been provisioned, you must configure the internal network, EDGE Gateway, and prepare the virtual machine template. Follow the instructions for setting up the environment in the provider’s documentation.

Go back Next: Installation