open-consul/agent/proxycfg-glue
Derek Menteer 1c4640f0df
Fix issue with peer services incorrectly appearing as connect-enabled. (#16339)
Prior to this commit, all peer services were transmitted as connect-enabled
as long as a one or more mesh-gateways were healthy. With this change, there
is now a difference between typical services and connect services transmitted
via peering.

A service will be reported as "connect-enabled" as long as any of these
conditions are met:

1. a connect-proxy sidecar is registered for the service name.
2. a connect-native instance of the service is registered.
3. a service resolver / splitter / router is registered for the service name.
4. a terminating gateway has registered the service.
2023-02-21 13:59:36 -06:00
..
config_entry.go
config_entry_test.go
discovery_chain.go
discovery_chain_test.go
exported_peered_services.go
exported_peered_services_test.go
federation_state_list_mesh_gateways.go
federation_state_list_mesh_gateways_test.go
gateway_services.go
gateway_services_test.go
glue.go
health.go
health_test.go
helpers_test.go
intention_upstreams.go
intention_upstreams_test.go
intentions.go
intentions_ent_test.go
intentions_oss.go
intentions_test.go
internal_service_dump.go
internal_service_dump_test.go
peered_upstreams.go
peered_upstreams_test.go
peering_list.go
peering_list_test.go
resolved_service_config.go
resolved_service_config_test.go
service_http_checks.go
service_http_checks_test.go
service_list.go
service_list_test.go
trust_bundle.go
trust_bundle_test.go