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

Switch fronend-service and backend-service

This commit is contained in:
boruszak 2022-06-15 14:07:56 -05:00
parent 96fb08ef61
commit ef4d603972
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
website/content/docs/connect/cluster-peering/create-manage-peering.mdx
View File

@ -98,17 +98,17 @@ Before you proceed, wait for the clusters to sync and make services available to
Before you can call services from peered clusters, you must set service intentions that authorize those clusters to use specific services. Consul prevents services from being exported to unauthorized clusters. Before you can call services from peered clusters, you must set service intentions that authorize those clusters to use specific services. Consul prevents services from being exported to unauthorized clusters.
First, create a configuration entry and specify the `Kind` as `“service-intentions”`. Declare the service on "cluster-02" that can access the service in "cluster-01." The following example sets service intentions so that "backend-service" can access "frontend-service." First, create a configuration entry and specify the `Kind` as `“service-intentions”`. Declare the service on "cluster-02" that can access the service in "cluster-01." The following example sets service intentions so that "frontend-service" can access "backend-service."
<CodeBlockConfig filename="peering-intentions.hcl" highlight="1" hideClipboard> <CodeBlockConfig filename="peering-intentions.hcl" highlight="1" hideClipboard>
```hcl ```hcl
Kind = "service-intentions" Kind = "service-intentions"
Name = "frontend-service" Name = "backend"-service"
Sources = [ Sources = [
{ {
Name = "backend-service" Name = "frontend-service"
Peer = "cluster-02" Peer = "cluster-02"
Action = "allow" Action = "allow"
} }