github
/
consul
mirror of https://github.com/hashicorp/consul
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

docs: Update k8s/connect/create-sameness-groups

pull/20317/head
Krastin Krastev 2024-01-23 12:22:31 +02:00 committed by GitHub
parent b37fe80eee
commit ad1d4f30de
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
website/content/docs/k8s/connect/cluster-peering/usage/create-sameness-groups.mdx
View File

@ -146,7 +146,7 @@ The following example demonstrates how to format three different `ExportedServic
apiVersion: consul.hashicorp.com/v1alpha1
Kind: ExportedServices
metadata:
name: product-group-export
name: partition-1
spec:
services:
- name: api
@ -163,7 +163,7 @@ spec:
apiVersion: consul.hashicorp.com/v1alpha1
Kind: ExportedServices
metadata:
name: product-group-export
name: partition-2
spec:
services:
- name: api
@ -180,7 +180,7 @@ spec:
apiVersion: consul.hashicorp.com/v1alpha1
Kind: ExportedServices
metadata:
name: product-group-export
name: partition-1
spec:
services:
- name: api
@ -291,4 +291,4 @@ If your goal for peering clusters is to create a sameness group, you can write a
When `defaultForFailover=true` in a sameness group CRD, additional upstream configuration is not required.
After creating a sameness group, you can also set up failover between services in a sameness group. Refer to [Failover with sameness groups](/consul/docs/connect/manage-traffic/failover/sameness) for more information.
After creating a sameness group, you can also set up failover between services in a sameness group. Refer to [Failover with sameness groups](/consul/docs/connect/manage-traffic/failover/sameness) for more information.