Update create-sameness-groups.mdx (#17927)

This commit is contained in:
David Yu 2023-06-27 20:23:03 -07:00 committed by GitHub
parent 6f5da97d66
commit b168132176
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 10 deletions

View File

@ -89,9 +89,9 @@ metadata:
spec:
defaultForFailover: true
members:
partition: partition-1
partition: partition-2
peer: dc2-partition-1
- partition: partition-1
- partition: partition-2
- peer: dc2-partition-1
```
</CodeBlockConfig>
@ -106,9 +106,9 @@ metadata:
spec:
defaultForFailover: true
members:
partition: partition-2
partition: partition-1
peer: dc2-partition-1
- partition: partition-2
- partition: partition-1
- peer: dc2-partition-1
```
</CodeBlockConfig>
@ -123,9 +123,9 @@ metadata:
spec:
defaultForFailover: true
members:
partition: partition-1
peer: dc1-partition-1
peer: dc2-partition-2
- partition: partition-1
- peer: dc1-partition-1
- peer: dc2-partition-2
```
</CodeBlockConfig>
@ -287,4 +287,4 @@ $ kubectl apply --filename api.yaml
It is possible to combine the service intentions configuration entry for creating sameness groups with the entry required to [authorize services for peers](/consul/docs/connect/cluster-peering/usage/establish-cluster-peering#authorize-services-for-peers).
In this workflow, configure the `sources` block with the `samenessGroup` field instead of the `peer` field. You should write the `sameness-group` configuration entry to Consul before referencing it in the `service-intentions` configuration entry.
In this workflow, configure the `sources` block with the `samenessGroup` field instead of the `peer` field. You should write the `sameness-group` configuration entry to Consul before referencing it in the `service-intentions` configuration entry.