Skip to main content
Skip table of contents

Install Related Version Information

Other helpful links for versions required to successfully run with DKP for the latest version can be found below and also in their respective section of Documentation.

Supported Kubernetes Version

Deploying Clusters Versions

The latest supported Kubernetes versions for DKP are listed below. In DKP 2.6.2, the Kubernetes version installed by default is 1.26.14. The newest and oldest Kubernetes versions used with DKP must be within one minor version.

  • Latest supported Kubernetes version is at 1.26.14 for deploying clusters

  • Other Kubernetes versions are supported at 1.25.13 for deploying clusters in EKS

Kubernetes 1.26.14 enables you to benefit from the latest features and security fixes in upstream Kubernetes. This release comes with approximately 40 enhancements that you can benefit from like Service internal tracking policy, Kubelet credential provider, among others. To read more about major features in this release, visit GitHub and https://kubernetes.io/blog/2022/12/09/kubernetes-v1-26-release/.

Attaching Clusters Versions

DKP 2.6.2 supports attaching clusters with the following Kubernetes versions:

Product

Compatible Kubernetes Versions

EKS

1.25.13

AKS

1.26.10

GKE

1.26.x

Attaching Kubernetes clusters with versions greater than n-1 is not recommended.

When attempting to attach a cluster with a lower Kubernetes version than the DKP default, you need to build and use an image with that lower version of Kubernetes. See Konvoy Image Builder for documentation on building images. Failure to do this could result in an error.

Konvoy Image Builder

Refer to the main page for a table of components versions and compatibility.

Storage Providers

Default storage providers in DKP

When deploying DKP using a supported cloud provisioner (AWS, Azure, GCP), DKP automatically configures native storage drivers for the target platform. In addition, DKP deploys a default StorageClass for https://kubernetes.io/docs/concepts/storage/dynamic-provisioning/ creation. The table below lists the driver and default StorageClass for each supported cloud provisioner.

Cloud Provisioner

Version

Driver

Default Storage Class

AWS

1.23

aws-ebs-csi-driver

ebs-sc

Azure

1.29.0

azuredisk-csi-driver

azuredisk-sc

Pre-provisioned

2.5.0

local-static-provisioner

localvolumeprovisioner

vSphere

2.7.2

vsphere-csi-driver

vsphere-raw-block-sc

Cloud Director (VCD)

main

cloud-director-named-csi-driver

vcd-disk-sc

GCP

1.10.3

gcp-compute-persistent-disk-csi-driver

csi-gce-pd

DKP uses the local static provisioner as the default storage provider for Pre-provisioned clusters. However, localvolumeprovisioner is not suitable for production use. You should use a Kubernetes CSI compatible storage that is suitable for production.

You can choose from any of the storage options available for Kubernetes. To disable the default that Konvoy deploys, set the default StorageClasslocalvolumeprovisioner as non-default. Then set your newly created StorageClass to be the default by following the commands in the Kubernetes documentation called Changing the Default Storage Class.

Deploying a Cluster in FIPS mode

In order to create a cluster in FIPS mode, we must inform the bootstrap controllers of the appropriate image repository and version tags of the official D2iQ FIPS builds of Kubernetes.

Supported FIPS Builds

Component

Repository

Version

Kubernetes

docker.io/mesosphere

v1.26.14+fips.0

etcd

docker.io/mesosphere

3.5.10+fips.0

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.