mirror of
https://github.com/hashicorp/vault.git
synced 2026-06-11 09:51:16 -04:00
Add Consul Dataplane compatibility info to docs (#18041)
* add compatibility info to consul service reg docs * fix alert formatting * add consul dataplane compatibility partial * add compat partial to more consul doc pages * fix links
This commit is contained in:
parent
0f0fe198ad
commit
7d9bc82bee
6 changed files with 11 additions and 0 deletions
|
|
@ -8,6 +8,8 @@ description: This is the API documentation for the Vault Consul secrets engine.
|
|||
|
||||
@include 'x509-sha1-deprecation.mdx'
|
||||
|
||||
@include 'consul-dataplane-compat.mdx'
|
||||
|
||||
This is the API documentation for the Vault Consul secrets engine. For general
|
||||
information about the usage and operation of the Consul secrets engine, please
|
||||
see the [Vault Consul documentation](/docs/secrets/consul).
|
||||
|
|
|
|||
|
|
@ -16,6 +16,8 @@ a default health check. When Consul is configured as the storage backend, the st
|
|||
|
||||
~> **Version information:** The `service_registration` configuration option was introduced in Vault 1.4.0.
|
||||
|
||||
@include 'consul-dataplane-compat.mdx'
|
||||
|
||||
- **HashiCorp Supported** – Consul Service Registration is officially supported
|
||||
by HashiCorp.
|
||||
|
||||
|
|
|
|||
|
|
@ -15,6 +15,8 @@ key-value store. In addition to providing durable storage, inclusion of this
|
|||
backend will also register Vault as a service in Consul with a default health
|
||||
check.
|
||||
|
||||
@include 'consul-dataplane-compat.mdx'
|
||||
|
||||
- **High Availability** – the Consul storage backend supports high availability.
|
||||
|
||||
- **HashiCorp Supported** – the Consul storage backend is officially supported
|
||||
|
|
|
|||
|
|
@ -10,6 +10,8 @@ description: |-
|
|||
|
||||
@include 'helm/version.mdx'
|
||||
|
||||
@include 'consul-dataplane-compat.mdx'
|
||||
|
||||
The below `values.yaml` can be used to set up a five server Vault cluster using
|
||||
Consul as a highly available storage backend, Google Cloud KMS for Auto Unseal.
|
||||
|
||||
|
|
|
|||
|
|
@ -8,6 +8,8 @@ description: The Consul secrets engine for Vault generates tokens for Consul dyn
|
|||
|
||||
@include 'x509-sha1-deprecation.mdx'
|
||||
|
||||
@include 'consul-dataplane-compat.mdx'
|
||||
|
||||
The Consul secrets engine generates [Consul](https://www.consul.io/) API tokens
|
||||
dynamically based on Consul ACL policies.
|
||||
|
||||
|
|
|
|||
1
website/content/partials/consul-dataplane-compat.mdx
Normal file
1
website/content/partials/consul-dataplane-compat.mdx
Normal file
|
|
@ -0,0 +1 @@
|
|||
~> **Compatibility information:** As of Consul 1.14.0, Consul on Kubernetes uses [Consul Dataplane](https://developer.hashicorp.com/consul/docs/connect/dataplane) by default instead of client agents. Vault does not currently support Consul Dataplane. Please follow the Consul 1.14.0 [upgrade guide](https://developer.hashicorp.com/consul/docs/k8s/upgrade#upgrading-to-consul-dataplane) to ensure that your Consul on Kubernetes deployment continues to use client agents.
|
||||
Loading…
Reference in a new issue