connect: allow configuration of "outlier detection" #6832
Labels
theme/connect
Anything related to Consul Connect, Service Mesh, Side Car Proxies
theme/envoy/xds
Related to Envoy support
type/enhancement
Proposed improvement or new feature
Milestone
Scope:
Allow configuration of Envoy's client side outlier detection.
Envoy names this feature "outlier detection" while uses the term "circuit breaker" to refer to connection pool limits. Many other systems tend to use "circuit breaker" to describe this pattern of avoiding sending traffic to nodes which have recently failed. See https://martinfowler.com/bliki/CircuitBreaker.html
We should carefully consider how we expose the config here as we want to be proxy-agnostic and other proxies use different terminology. We might avoid the term "circuit breaker" just because that means something else in Envoy land.
It would be good to review how similar controls are implemented in other major proxies (HAProxy, Nginx at least) to make sure we come up with something that is meaningful for all ideally or can discuss the best tradeoff otherwise.
One term I think works reasonably well here is "Passive health checking".
It would be ideal to be able to specify global defaults in the global
proxy-defaults
ConfigEntry that would be inherited by services that don't explicitly set their own. Otherwise this is expected to live inservice-defaults
(or wherever we decide upstream defaults go as part of #6359).The text was updated successfully, but these errors were encountered: