mirror of https://github.com/status-im/consul.git
51 lines
3.4 KiB
Plaintext
51 lines
3.4 KiB
Plaintext
---
|
|
layout: docs
|
|
page_title: Consul on Kubernetes Version Compatibility
|
|
description: >-
|
|
New releases require corresponding version updates to Consul on Kubernetes and its Helm chart. Review the compatibility matrix for Consul and consul-k8s and additional notes for integrating Vault and third-party platforms.
|
|
---
|
|
|
|
# Consul on Kubernetes Version Compatibility
|
|
|
|
For every release of Consul on Kubernetes, a Helm chart, `consul-k8s-control-plane` binary and a `consul-k8s` CLI binary is built and distributed through a single version. When deploying via Helm, the recommended best path for upgrading Consul on Kubernetes, is to upgrade using the same `consul-k8s-control-plane` version as the Helm Chart, as the Helm Chart and Control Plane binary are tightly coupled.
|
|
|
|
## Supported Consul versions
|
|
|
|
Consul Kubernetes versions all of its components (`consul-k8s` CLI, `consul-k8s-control-plane`, and Helm chart) with a single semantic version. When installing or upgrading to a specific versions, ensure that you are using the correct Consul version with the compatible `consul-k8s` helm chart and/or CLI.
|
|
|
|
| Consul Version | Compatible consul-k8s Versions |
|
|
| -------------- | -------------------------------- |
|
|
| 1.13.x | 0.47.0 - latest |
|
|
| 1.12.x | 0.43.0 - latest |
|
|
| 1.11.x | 0.39.0 - 0.42.0, 0.44.0 - latest |
|
|
|
|
## Supported Envoy versions
|
|
|
|
Supported versions of Envoy for Consul versions are also found in [Envoy - Supported Versions](/docs/connect/proxies/envoy#supported-versions). The recommended best practice is to use the default version of Envoy that is provided in the Helm values.yml file, as that is the version that has been tested with the default Consul and Consul Kubernetes binaries for a given Helm chart.
|
|
|
|
## Vault as a Secrets Backend compatibility
|
|
|
|
Starting with Consul K8s 0.39.0 and Consul 1.11.x, Consul Kubernetes supports the ability to utilize Vault as the secrets backend for all the secrets utilized by Consul on Kubernetes.
|
|
|
|
| `consul-k8s` Versions | Compatible Vault Versions | Compatible `vault-k8s` Versions |
|
|
| ------------------------ | --------------------------| ----------------------------- |
|
|
| 0.39.0 - latest | 1.9.0 - latest | 0.14.0 - latest |
|
|
|
|
## Platform specific compatibility notes
|
|
|
|
### Red Hat OpenShift
|
|
|
|
Consul Kubernetes delivered Red Hat OpenShift support starting with Consul Helm chart version 0.25.0 for Consul 1.8.4. Please note the following details regarding OpenShift support.
|
|
|
|
- Red Hat OpenShift is only supported for OpenShift 4.4.x and above.
|
|
- Only the default CNI Plugin, [OpenShift SDN CNI Plugin](https://docs.openshift.com/container-platform/4.9/networking/openshift_sdn/about-openshift-sdn.html) is currently supported.
|
|
|
|
### VMware Tanzu Kubernetes Grid and Tanzu Kubernetes Grid Integrated Edition
|
|
|
|
Consul Kubernetes is [certified](https://marketplace.cloud.vmware.com/services/details/hashicorp-consul-1?slug=true) for both VMware Tanzu Kubernetes Grid, and VMware Tanzu Kubernetes Integrated Edition.
|
|
|
|
- Tanzu Kubernetes Grid is certified for version 1.3.0 and above. Only Calico is supported as the CNI Plugin.
|
|
- Tanzu Kubernetes Grid Integrated Edition is supported for version 1.11.1 and above. [NSX-T CNI Plugin v3.1.2](https://docs.vmware.com/en/VMware-NSX-T-Data-Center/3.1/rn/NSX-Container-Plugin-312-Release-Notes.html) and greater should be used and configured with the `enable_hostport_snat` setting set to `true`.
|
|
|
|
|