mirror of https://github.com/status-im/consul.git
/docs/connect/registration
This commit is contained in:
parent
9c5de92d9f
commit
f76983f1fb
|
@ -1,13 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Connect - Proxy Registration
|
||||
page_title: Service Mesh Proxy: Overview
|
||||
description: >-
|
||||
To make connect aware of proxies you will need to register them as Consul
|
||||
services. This section describes the process and options for proxy
|
||||
registration.
|
||||
To make Consul aware of proxies in your service mesh, you must register them. Learn more about proxy registration and sidecar service registration, including differences in how registering works.
|
||||
---
|
||||
|
||||
# Proxy Registration
|
||||
# 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.
|
||||
|
|
|
@ -1,13 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Connect - Service Registration
|
||||
page_title: Service Mesh Proxy: Configuration
|
||||
description: >-
|
||||
A per-service proxy sidecar transparently handles inbound and outbound service
|
||||
connections. You can register these sidecars with reasonable defaults by nesting
|
||||
their definitions in the service definition.
|
||||
Use service mesh proxy configuration files to define the parameters and behaviors of custom proxies deployed with services in your mesh. Learn about configuration options and how to format them with examples.
|
||||
---
|
||||
|
||||
# Proxy Service Registration
|
||||
# Service Mesh Proxy Configuration
|
||||
|
||||
This topic describes how to declare a proxy as a `connect-proxy` in service definitions. The `kind` must be declared and information about the service they represent must be provided to function as a Consul service mesh proxy.
|
||||
|
||||
|
|
|
@ -1,12 +1,11 @@
|
|||
---
|
||||
layout: docs
|
||||
page_title: Connect - Sidecar Service Registration
|
||||
description: |-
|
||||
Sidecar service registrations provide a convenient shorthand for registering a
|
||||
sidecar proxy inline with a regular service definition.
|
||||
page_title: Service Mesh Proxy: Sidecar Configuration
|
||||
description: >-
|
||||
In a service mesh, sidecar proxies run in the same node as service instances and are configured in service definition files. Learn about default settings, customizable parameters, limitations, and lifecycle behaviors.
|
||||
---
|
||||
|
||||
# Sidecar Service Registration
|
||||
# Service Mesh Proxy Sidecar Configuration
|
||||
|
||||
Connect proxies are typically deployed as "sidecars" that run on the same node
|
||||
as the single service instance that they handle traffic for. They might be on
|
||||
|
|
Loading…
Reference in New Issue