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

Remove global.name requirement for APs (#16964) 

This is not a requirement when using APs because each AP has its own
auth method so it's okay if the names overlap.
This commit is contained in:
Luke Kysow 2023-04-11 11:41:33 -07:00 committed by GitHub
parent d46543631c
commit f6603008d1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -112,7 +112,6 @@ One of the primary use cases for admin partitions is for enabling a service mesh
- If you are deploying Consul servers on Kubernetes, then ensure that the Consul servers are deployed within the same Kubernetes cluster. Consul servers may be deployed external to Kubernetes and configured using the `externalServers` stanza.
- Workloads deployed on the same Kubernetes cluster as the Consul Servers must use the `default` partition. If the workloads are required to run on a non-default partition, then the clients must be deployed in a separate Kubernetes cluster.
- For Kubernetes clusters that join the Consul datacenter as admin partitions, ensure that a unique `global.name` value is assigned for the corresponding Helm `values.yaml` file.
- A Consul Enterprise license must be installed on each Kubernetes cluster.
- The helm chart for consul-k8s v0.39.0 or greater.
- Consul 1.11.1-ent or greater.
@ -245,7 +244,6 @@ Verify that your Consul deployment meets the [Kubernetes Requirements](#kubernet
```
1. Create a configuration for each non-default admin partition.
In the following example, the external IP address and the Kubernetes authentication method IP address from the previous steps have been applied. Also, ensure a unique `global.name` value is assigned.
<CodeTabs heading="partition-workload.yaml">