luxolus
/
open-consul
2
0
Fork 0
Code Issues 1 Pull Requests Packages Releases Wiki Activity

docs: Update Consul K8s compatibility matrix (#12829) 

* docs: Update Consul K8s compatibility matrix

Co-authored-by: Karl Cardenas <kcardenas@hashicorp.com>
This commit is contained in:
David Yu 2022-04-21 10:10:56 -07:00 committed by GitHub
parent 2b8f10feec
commit 0ac00c75e4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 21 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
website/content/docs/k8s/installation/compatibility.mdx
View File

@ -16,7 +16,8 @@ Starting with Consul Kubernetes 0.33.0, Consul Kubernetes versions all of its co
| Consul Version | Compatible consul-k8s Versions |
| -------------- | ------------------------------- |
| 1.11.x | 0.39.0 - latest |
| 1.12.x | 0.43.0 - latest |
| 1.11.x | 0.39.0 - 0.42.0 |
| 1.10.x | 0.33.0 - 0.38.0 |
### Prior to version 0.33.0
@ -35,13 +36,6 @@ Prior to Consul Kubernetes 0.33.0, a separately versioned Consul Helm chart was
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.
## Red Hat OpenShift compatibility
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.
## 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.
@ -50,3 +44,20 @@ Starting with Consul K8s 0.39.0 and Consul 1.11.x, Consul Kubernetes supports th
| ------------------------ | --------------------------| ----------------------------- |
| 0.39.0 - latest | 1.9.0 - latest | 0.14.0 - latest |
## Platform Specific compatability 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 Kuberntetes 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`.

3
website/content/docs/k8s/installation/vault/systems-integration.mdx
View File

@ -93,7 +93,8 @@ Before installing the Vault Injector and configuring the Vault Kubernetes Auth M
```shell-session
$ export VAULT_ADDR=http://${VAULT_SERVER_HOST}:8200
```
-> **Note:** If your vault installation is current exposed using SSL, this address will need to use `https` instead of `http`. You will also need to setup the [`VAULT_CACERT`](https://www.vaultproject.io/docs/commands#vault_cacert) environment variable.
-> **Note:** If your vault installation is current exposed using SSL, this address will need to use `https` instead of `http`. You will also need to setup the [`VAULT_CACERT`](https://www.vaultproject.io/docs/commands#vault_cacert) environment variable.
#### VAULT_TOKEN