status-im
/
consul
mirror of https://github.com/status-im/consul.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

docs: Admin Partitions image bump to GA (#11846) 

* docs: Admin Partitions image bump to GA
* Bump to the right versions for Consul 1.11.1
This commit is contained in:
David Yu 2021-12-15 15:37:46 -08:00 committed by GitHub
parent 1d5fba753c
commit 8504b689ab
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
website/content/docs/enterprise/admin-partitions.mdx
View File

@ -59,7 +59,7 @@ Your Consul configuration must meet the following requirements to use admin part
### Versions ### Versions
* Consul 1.11.0 and newer * Consul 1.11.1 and newer
### Security Configurations ### Security Configurations
@ -84,8 +84,8 @@ One of the primary use cases for admin partitions is for enabling a service mesh
* Two or more Kubernetes clusters. Consul servers must be deployed to a single cluster. The other clusters should run Consul clients. * Two or more Kubernetes clusters. Consul servers must be deployed to a single cluster. The other clusters should run Consul clients.
* A Consul Enterprise license must be installed on each Kubernetes cluster. * A Consul Enterprise license must be installed on each Kubernetes cluster.
* The helm chart for consul-k8s v0.38.0 or greater. * The helm chart for consul-k8s v0.39.0 or greater.
* Consul 1.11.0-ent or greater. * Consul 1.11.1-ent or greater.
* All Consul clients must be able to communicate with the Consul servers in the `default` partition, and all servers must be able to communicate with the clients. * All Consul clients must be able to communicate with the Consul servers in the `default` partition, and all servers must be able to communicate with the clients.
## Usage ## Usage
@ -118,7 +118,7 @@ Verify that your Consul deployment meets the [Kubernetes Requirements](#kubernet
enableConsulNamespaces: true enableConsulNamespaces: true
tls: tls:
enabled: true enabled: true
image: hashicorp/consul-enterprise:1.11.0-ent-rc image: hashicorp/consul-enterprise:1.11.1-ent
adminPartitions: adminPartitions:
enabled: true enabled: true
acls: acls:
@ -194,7 +194,7 @@ Verify that your Consul deployment meets the [Kubernetes Requirements](#kubernet
global: global:
enabled: false enabled: false
enableConsulNamespaces: true enableConsulNamespaces: true
image: hashicorp/consul-enterprise:1.11.0-ent-rc image: hashicorp/consul-enterprise:1.11.1-ent
adminPartitions: adminPartitions:
enabled: true enabled: true
name: clients name: clients
@ -266,4 +266,4 @@ You will see the `default` and `clients` partitions available in the **Admin Par
## Known Limitations ## Known Limitations
* Only the `default` admin partition is supported when federating multiple Consul datacenters in a WAN. * Only the `default` admin partition is supported when federating multiple Consul datacenters in a WAN.