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

docs: Service Sync clarify requirements when using Service Mesh (#12177) 

* docs: Service Sync clarify requirements when using Service Mesh

* replace with relative link
This commit is contained in:
David Yu 2022-01-25 15:02:19 -08:00 committed by GitHub
parent 64e9e8a574
commit b199b60ded
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/content/docs/k8s/service-sync.mdx
View File

@ -32,6 +32,8 @@ service discovery, including hosted services like databases.
## Installation and Configuration
~> Enabling both Service Mesh and Service Sync on the same Kubernetes services is not supported, as Service Mesh also registers Kubernetes service instances to Consul. Please ensure that Service Sync is only enabled for namespaces and services that are not injected with the Consul sidecar for Service Mesh as described in [Sync Enable/Disable](/docs/k8s/service-sync#sync-enable-disable).
The service sync is done using an external long-running process in the
[consul-k8s project](https://github.com/hashicorp/consul-k8s). This process
can run either in or out of a Kubernetes cluster. However, running this within