The table below shows the versions of Kubernetes on which Domino validates its software. Validation is performed for the following providers: AWS, Azure, Google Cloud, Red Hat OpenShift, and Rancher.
For security and stability, Domino encourages customers to keep their Kubernetes infrastructure up to date running a version of Domino we’ve officially validated. Outdated or unvalidated combinations of Domino and Kubernetes may affect the supportability of your deployment.
Every 12-14 months, Kubernetes versions reach end-of-life (EOL) and may no longer be supported by the Kubernetes provider. If you have questions about the compatibility and upgrade path, contact Domino customer support for assistance.
Work with Domino to align your installation and upgrade planning with the guidance below:
-
Domino ships major or minor releases approximately every 3 months. Strive to keep your Domino deployments updated with the latest releases by upgrading every 3 to 6 months. Skipping multiple versions of Domino results in larger gaps in Kubernetes version compatibility and more complex upgrades.
-
Each Kubernetes provider has a different release schedule for specific versions of Kubernetes. Domino strives to support new Kubernetes releases within approximately 3 months of the generally available release date.
-
Domino should be upgraded onto a supported Kubernetes version (see compatibility table below). When you upgrade Kubernetes, you should immediately upgrade to a supported Domino version.
-
Domino recommends keeping Kubernetes control plane and data plane at the same version, minimizing version skew.
Domino Nexus hybrid deployments
Nexus control planes require the same Kubernetes cluster requirements as any other Domino deployment.
However, Nexus data planes have the following differences:
-
No requirement for shared storage (RWX storage class).
-
Requires only one (compute) namespace.
-
Ingress configuration is different, see Enable a Data Plane for Workspaces for more information.
The following matrix shows the supported combinations of Domino and Kubernetes platform versions. For inquiry about unlisted Kubernetes distributions, contact your Domino professional services representative.
End of life (EOL) for Kubernetes versions is dictated by the Kubernetes platform provider. For more information on what EOL means for each platform, see the links in the Kubernetes Platform column.
|
Note
| EKS version 1.24 requires the use of EKS optimized Amazon Linux AMI release 1.24.7-20221222 or later. |
| Domino Version | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
Kubernetes Platform | 6.0.x | 5.11.x | 5.10.x | 5.9.x | 5.8.x | 5.7.x | 5.6.x | 5.5.x | 5.4.x | 5.3.x | 5.2.x | 5.1.x |
1.30 | 1.28 | 1.27 | 1.27 | 1.26 | 1.25 | 1.24 | 1.23 | 1.23 | 1.23 | 1.22 (EOL) | 1.21 (EOL) | |
1.29 | 1.29 | 1.28 | 1.28 | 1.27 | 1.26 | 1.25 | 1.24 | 1.24 | 1.24 | 1.22 (EOL) | ||
1.30 | 1.28 | 1.27 | 1.27 | 1.26 | 1.25 (EOL) | 1.24 (EOL) | 1.24 (EOL) | 1.23 (EOL) | 1.23 (EOL) | 1.22 (EOL) | 1.21 (EOL) | |
1.29 | 1.29 | 1.28 | 1.28 | 1.27 | 1.26 | 1.25 (EOL) | 1.25 (EOL) | 1.24 (EOL) | ||||
1.30 | 1.28 | 1.27 | 1.26 | 1.26 | 1.25 (EOL) | 1.24 (EOL) | 1.24 (EOL) | 1.23 (EOL) | 1.23 (EOL) | 1.22 (EOL) | 1.21 (EOL) | |
1.29 | 1.29 | 1.28 | 1.27 | 1.27 | 1.26 | 1.25 (EOL) | 1.25 (EOL) | 1.24 (EOL) | 1.24 (EOL) | |||
1.29 (4.16) | 1.28 (4.15) | 1.27 (4.14) | 1.27 (4.14) | 1.26 (4.13) | 1.26 (4.13) | 1.25 (4.12) | 1.24 (4.11) | 1.24 (4.11) | ||||
Rancher | 1.28 (2.8.3) | 1.27 (2.8.3) | 1.26 (2.7.9) | 1.26 (2.7.6) | 1.26 (2.7.6) | 1.26 (2.7.5) | 1.24 (2.7.1) | 1.24 (2.7.1) | 1.23 (2.6.7) | 1.23 (2.6.7) | 1.19 (2.5.8) | |
1.27 (2.8.3) | 1.28 (2.8.3) | |||||||||||
Domino doesn’t publish a validated container runtime compatibility matrix and recommends using the default container runtime version provided by your vendor. However, if your Kubernetes nodes use Docker, it should be 20.10.24 or higher.