luxolus
/
open-vault
2
0
Fork 0
Code Issues 1 Pull Requests Releases Activity

mention Consul Dataplane compat in 1.13.x upgrade notes (#18063) 

* mention Consul Dataplane compat in 1.13.x upgrade notes

* change heading level

Co-authored-by: Meggie <meggie@hashicorp.com>

Co-authored-by: Meggie <meggie@hashicorp.com>
This commit is contained in:
Chris Capurso 2022-11-21 14:11:13 -05:00 committed by GitHub
parent b51b2a7027
commit d392754914
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/content/docs/upgrading/upgrade-to-1.13.x.mdx
View File

@ -16,6 +16,8 @@ for Vault 1.13.x compared to 1.12. Please read it carefully.
## Changes
@include 'consul-dataplane-upgrade-note.mdx'
### AliCloud Auth Role Parameter
The AliCloud auth plugin will now require the `role` parameter on login. This

2
website/content/partials/consul-dataplane-upgrade-note.mdx Normal file
View File

@ -0,0 +1,2 @@
### Consul Dataplane Compatibility
If you are using Consul on Kubernetes, please be aware that upgrading to Consul 1.14.0 will impact Consul [secrets](/docs/secrets/consul), [storage](/docs/configuration/storage/consul), and [service registration](/docs/configuration/service-registration/consul). 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.