mirror of https://github.com/hashicorp/consul
24 lines
1.4 KiB
Markdown
24 lines
1.4 KiB
Markdown
---
|
|
layout: docs
|
|
page_title: Service Mesh Proxy Registration Overview
|
|
description: >-
|
|
To make Consul aware of proxies in your service mesh, you must register them. Learn about methods for configuring and registering sidecar proxies.
|
|
---
|
|
|
|
# Service Mesh Proxy Overview
|
|
|
|
To make Connect aware of proxies you will need to register them in a [service
|
|
definition](/docs/discovery/services), just like you would register any other service with Consul. This section outlines your options for registering Connect proxies, either using independent registrations, or in nested sidecar registrations.
|
|
|
|
## Proxy Service Registration
|
|
|
|
To register proxies with independent proxy service registrations, you can define them in either in config files or via the API just like any other service. Learn more about all of the options you can define when registering your proxy service in the [proxy registration documentation](/docs/connect/registration/service-registration).
|
|
|
|
## Sidecar Service Registration
|
|
|
|
To reduce the amount of boilerplate needed for a sidecar proxy,
|
|
application service definitions may define an inline sidecar service block. This is an opinionated
|
|
shorthand for a separate full proxy registration as described above. For a
|
|
description of how to configure the sidecar proxy as well as the opinionated defaults, see the [sidecar service registrations
|
|
documentation](/docs/connect/registration/sidecar-service).
|