* connect: remove managed proxies implementation and all supporting config options and structs * connect: remove deprecated ProxyDestination * command: remove CONNECT_PROXY_TOKEN env var * agent: remove entire proxyprocess proxy manager * test: remove all managed proxy tests * test: remove irrelevant managed proxy note from TestService_ServerTLSConfig * test: update ContentHash to reflect managed proxy removal * test: remove deprecated ProxyDestination test * telemetry: remove managed proxy note * http: remove /v1/agent/connect/proxy endpoint * ci: remove deprecated test exclusion * website: update managed proxies deprecation page to note removal * website: remove managed proxy configuration API docs * website: remove managed proxy note from built-in proxy config * website: add note on removing proxy subdirectory of data_dir
1.7 KiB
layout | page_title | sidebar_current | description |
---|---|---|---|
docs | Connect - Proxies | docs-connect-proxies | A Connect-aware proxy enables unmodified applications to use Connect. This section details how to use either Envoy or Consul's built-in L4 proxy, and describes how you can plug in a proxy of your choice. |
Connect Proxies
A Connect-aware proxy enables unmodified applications to use Connect. A per-service proxy sidecar transparently handles inbound and outbound service connections, automatically wrapping and verifying TLS connections. Consul includes its own built-in L4 proxy and has first class support for Envoy. You can choose other proxies to plug in as well. This section describes how to configure Envoy or the built-in proxy using Connect, and how to integrate the proxy of your choice.
To ensure that services only allow external connections established via the Connect protocol, you should configure all services to only accept connections on a loopback address.
~> Deprecation Note: Managed Proxies are a deprecated method for deploying sidecar proxies, and have been removed in Consul 1.6. See managed proxy deprecation for more information. If you are using managed proxies we strongly recommend that you switch service definitions for registering proxies.
Dynamic Upstreams Require Native Integration
If an application requires dynamic dependencies that are only available at runtime, it must natively integrate with Connect. After natively integrating, the HTTP API or DNS interface can be used.
!> Connect proxies do not currently support dynamic upstreams.