Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Backport of Add Consul Dataplane compatibility info to docs into release/1.12.x #18076

Merged
merged 2 commits into from Nov 22, 2022
Merged

Backport of Add Consul Dataplane compatibility info to docs into release/1.12.x #18076

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ebc5ebb
backport of commit 7d9bc82beee0681f49f349f92d9127dfcaaf9e5f
ccapurso Nov 22, 2022
86df833
Merge branch 'release/1.12.x' into backport/consul-k8s-agentless-docs…
ccapurso Nov 22, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 2 additions & 0 deletions website/content/api-docs/secret/consul.mdx
View file
Open in desktop
Expand Up @@ -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).
Expand Down
2 changes: 2 additions & 0 deletions website/content/docs/configuration/service-registration/consul.mdx
View file
Open in desktop
Expand Up @@ -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.

Expand Down
2 changes: 2 additions & 0 deletions website/content/docs/configuration/storage/consul.mdx
View file
Open in desktop
Expand Up @@ -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
Expand Down
2 changes: 2 additions & 0 deletions website/content/docs/platform/k8s/helm/examples/ha-with-consul.mdx
View file
Open in desktop
Expand Up @@ -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.

Expand Down
2 changes: 2 additions & 0 deletions website/content/docs/secrets/consul.mdx
View file
Open in desktop
Expand Up @@ -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.

Expand Down
1 change: 1 addition & 0 deletions website/content/partials/consul-dataplane-compat.mdx
View file
Open in desktop
@@ -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.