mirror of https://github.com/hashicorp/consul
add PD conf entry usage to appropro pages
parent
3345473c10
commit
d838e5de9e
|
@ -13,7 +13,7 @@ This topic describes how to create, register, and start service mesh proxies in
|
|||
|
||||
Complete the following steps to deploy a service mesh proxy:
|
||||
|
||||
1. It is not required, but you can create a proxy defaults configuration entry that contains global passthrough settings for all Envoy proxies. Refer to [Proxy defaults configuration entry reference](/consul/docs/connect/config-entries/proxy-defaults) for additional information.
|
||||
1. It is not required, but you can create a proxy defaults configuration entry that contains global passthrough settings for all Envoy proxies.
|
||||
1. Create a service definition file and specify the proxy configurations in the `proxy` block.
|
||||
1. Register the service using the API or CLI.
|
||||
1. Start the proxy service.
|
||||
|
@ -22,6 +22,16 @@ Complete the following steps to deploy a service mesh proxy:
|
|||
|
||||
If [ACLs](/consul/docs/security/acl) are enabled and you want to configure global Envoy settings in the [proxy defaults configuration entry](/consul/docs/connect/config-entries/proxy-defaults), you must present a token with `operator:write` permissions. Refer to [Create a service token](/consul/docs/security/acl/tokens/create/create-a-service-token) for additional information.
|
||||
|
||||
## Configure global Envoy passthrough settings
|
||||
|
||||
If you want to define global passthrough settings for all Envoy proxies, create a proxy defaults configuration entry and specify default settings, such as access log configuration. [Service defaults configuration entries](/consul/docs/connect/config-entries/service-defaults) override proxy defaults and individual service configurations override both configuration entries.
|
||||
|
||||
1. Create a proxy defaults configuration entry and specify the following parameters:
|
||||
- `Kind`: Must be set to `proxy-defaults`
|
||||
- `Name`: Must be set to `global`
|
||||
1. Configure any additional settings you want to apply to all proxies. Refer to [Proxy defaults configuration entry reference](/consul/docs/connect/config-entries/proxy-defaults) for details about all settings available in the configuraiton entry.
|
||||
1. Apply the configuration by either calling the [`/config` API endpoint](/consul/api-docs/config) or running the [`consul config write` CLI command](/consul/commands/config/write).
|
||||
|
||||
## Define service mesh proxy
|
||||
|
||||
Create a service definition file and configure the following fields to define a service mesh proxy:
|
||||
|
@ -29,10 +39,10 @@ Create a service definition file and configure the following fields to define a
|
|||
1. Set the `kind` field to `connect-proxy`. Refer to the [services configuration reference](/consul/docs/services/configuration/services-configuration-reference#kind) for information about other kinds of proxies you can declare.
|
||||
1. Specify a name for the proxy service in the `name` field. Consul applies the configurations to any proxies you bootstrap with the same name.
|
||||
1. In the `proxy.destination_service_name` field, specify the name of the service that the proxy represents.
|
||||
1. Configure any additional proxy behaviors that you want to implement in the `proxy` block. Refer to the [Service mesh proxy configuration reference](/consul/docs/connect/registration/service-registration) for information about all parameters.
|
||||
1. Configure any additional proxy behaviors that you want to implement in the `proxy` block. Refer to the [Service mesh proxy configuration reference](/consul/docs/connect/proxies/proxy-config-reference) for information about all parameters.
|
||||
1. Specify a port number where other services registered with Consul can discover and connect to the proxies service in the `port` field. To ensure that services only allow external connections established through the service mesh protocol, you should configure all services to only accept connections on a loopback address.
|
||||
|
||||
Refer to the [Service mesh proxy configuration reference](/consul/docs/connect/proxy-config-reference) for example configurations.
|
||||
Refer to the [Service mesh proxy configuration reference](/consul/docs/connect/proxies/proxy-config-reference) for example configurations.
|
||||
|
||||
## Register the service
|
||||
|
||||
|
|
|
@ -16,7 +16,7 @@ They may be on the same VM or running as a separate container in the same networ
|
|||
|
||||
You can attach a sidecar proxy to a service you want to deploy to your mesh:
|
||||
|
||||
1. It is not required, but you can create a proxy defaults configuration entry that contains global passthrough settings for all Envoy proxies. Refer to [Proxy defaults configuration entry reference](/consul/docs/connect/config-entries/proxy-defaults) for additional information.
|
||||
1. It is not required, but you can create a proxy defaults configuration entry that contains global passthrough settings for all Envoy proxies.
|
||||
1. Create the service definition and include the `connect` block. The `connect` block contains the sidecar proxy configurations that allow the service to interact with other services in the mesh.
|
||||
1. Register the service using either the API or CLI.
|
||||
1. Start the sidecar proxy service.
|
||||
|
@ -25,6 +25,16 @@ You can attach a sidecar proxy to a service you want to deploy to your mesh:
|
|||
|
||||
If [ACLs](/consul/docs/security/acl) are enabled and you want to configure global Envoy settings in the [proxy defaults configuration entry](/consul/docs/connect/config-entries/proxy-defaults), you must present a token with `operator:write` permissions. Refer to [Create a service token](/consul/docs/security/acl/tokens/create/create-a-service-token) for additional information.
|
||||
|
||||
## Configure global Envoy passthrough settings
|
||||
|
||||
If you want to define global passthrough settings for all Envoy proxies, create a proxy defaults configuration entry and specify default settings, such as access log configuration. [Service defaults configuration entries](/consul/docs/connect/config-entries/service-defaults) override proxy defaults and individual service configurations override both configuration entries.
|
||||
|
||||
1. Create a proxy defaults configuration entry and specify the following parameters:
|
||||
- `Kind`: Must be set to `proxy-defaults`
|
||||
- `Name`: Must be set to `global`
|
||||
1. Configure any additional settings you want to apply to all proxies. Refer to [Proxy defaults configuration entry reference](/consul/docs/connect/config-entries/proxy-defaults) for details about all settings available in the configuraiton entry.
|
||||
1. Apply the configuration by either calling the [`/config` API endpoint](/consul/api-docs/config) or running the [`consul config write` CLI command](/consul/commands/config/write).
|
||||
|
||||
## Define service mesh proxy
|
||||
|
||||
Create a service definition and configure the following fields:
|
||||
|
|
Loading…
Reference in New Issue