618deae657
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 |
||
|---|---|---|
| .. | ||
| bootstrap | ||
| config | ||
| discover | ||
| scada | ||
| testserver | ||
| client.go | ||
| deps.go | ||
| manager.go | ||
| manager_test.go | ||
| mock_Client.go | ||
| testing.go | ||