mirror of https://github.com/hashicorp/consul
3e3ab25f9b
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 Co-authored-by: Dan Upton <daniel@floppy.co> |
||
|---|---|---|
| .. | ||
| common.go | ||
| mock_Provider.go | ||
| provider.go | ||
| provider_aws.go | ||
| provider_aws_test.go | ||
| provider_consul.go | ||
| provider_consul_config.go | ||
| provider_consul_test.go | ||
| provider_test.go | ||
| provider_vault.go | ||
| provider_vault_test.go | ||
| testing.go | ||