consul

Commit Graph

Author	SHA1	Message	Date
Ashwin Venkatesh	797e42dc24	Watch the ProxyTracker from xDS controller (#18611 )	2023-08-29 14:39:29 -07:00
John Murret	0e606504bc	NET-4944 - wire up controllers with proxy tracker (#18603 ) Co-authored-by: github-team-consul-core <github-team-consul-core@hashicorp.com>	2023-08-29 09:15:34 -06:00
Dan Upton	7a55de375c	xds: don't attempt to load-balance sessions for local proxies (#15789 ) Previously, we'd begin a session with the xDS concurrency limiter regardless of whether the proxy was registered in the catalog or in the server's local agent state. This caused problems for users who run `consul connect envoy` directly against a server rather than a client agent, as the server's locally registered proxies wouldn't be included in the limiter's capacity. Now, the `ConfigSource` is responsible for beginning the session and we only do so for services in the catalog. Fixes: https://github.com/hashicorp/consul/issues/15753	2023-01-18 12:33:21 -06:00

Author

SHA1

Message

Date

Ashwin Venkatesh

797e42dc24

Watch the ProxyTracker from xDS controller (#18611 )

2023-08-29 14:39:29 -07:00

John Murret

0e606504bc

NET-4944 - wire up controllers with proxy tracker (#18603 )

Co-authored-by: github-team-consul-core <github-team-consul-core@hashicorp.com>

2023-08-29 09:15:34 -06:00

Dan Upton

7a55de375c

xds: don't attempt to load-balance sessions for local proxies (#15789 )

Previously, we'd begin a session with the xDS concurrency limiter
regardless of whether the proxy was registered in the catalog or in
the server's local agent state.

This caused problems for users who run `consul connect envoy` directly
against a server rather than a client agent, as the server's locally
registered proxies wouldn't be included in the limiter's capacity.

Now, the `ConfigSource` is responsible for beginning the session and we
only do so for services in the catalog.

Fixes: https://github.com/hashicorp/consul/issues/15753

2023-01-18 12:33:21 -06:00

3 Commits