status-im/consul
2
0
Fork 0
mirror of https://github.com/status-im/consul.git synced 2025-01-13 15:26:48 +00:00
Code Issues Projects Releases Wiki Activity

[NET-5916] docs: Remove locality proxy startup section (#19534)

Browse Source 
docs: Remove locality proxy startup section

This section is not necessary as it is not unique to the feature. The
instructions for starting proxies are available in other pages.
This commit is contained in:
Michael Zalimeni 2023-11-06 16:02:44 -05:00 committed by GitHub
parent c9f2a6add4
commit 90aa83fb0f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 0 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
website/content/docs/connect/manage-traffic/route-to-local-upstreams.mdx
View File

@ -103,17 +103,3 @@ You can configure the default routing behavior for all proxies in the mesh as we
```shell-session ```shell-session
$ consul config write web-resolver.hcl $ consul config write web-resolver.hcl
``` ```
## Start the proxies in your datacenter
Envoy requires a bootstrap configuration file before it can start. Use the [`consul connect envoy` command](/consul/commands/connect/envoy) to create the Envoy bootstrap configuration and start the sidecar proxy service. Specify the ID of the sidecar proxy you want to start with the `-sidecar-for` option.
The following example command starts an Envoy proxy for the `web` proxy service:
```shell-session
$ consul connect envoy -sidecar-for=web
```
For details about operating an Envoy proxy in Consul, refer to the [Envoy proxy reference](/consul/docs/connect/proxies/envoy).
Use the `/agent/service/register` API endpoint to register sidecars independently from their application services. You must include the `locality` configuration in the payload. Refer to [Register Service](/consul/api-docs/agent/service#register-service) in the API documentation for additional information.