envoyproxy / envoyproxy/gateway

Support listener health check modes

Offen
#5,699 7 Kommentare 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen
stale triage
Vorherrschende Sprache
Go
Sterne
3k
Forks
864
Ø Merge
2 T. 2 Std.
Gemergte PRs (30 T.)
140

Beschreibung

## Background

Envoy supports configuring the listener health check in 4 different modes: https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/health_checking#http-health-checking-filter

## Current Behavior

When a listener health endpoint is specified via [ClientTrafficPolicy.healthCheck](https://gateway.envoyproxy.io/docs/api/extension_types/#healthchecksettings), EG implicitly configures the health check listener in **No pass through** mode.

https://github.com/confluentinc/envoy-gateway/blob/d4aae99ef274c66927a4594fb20d2c877c48d3b8/internal/xds/translator/healthcheck.go#L71-L83

## Desired Behavior

ClientTrafficPolicy should expose knobs to configure the different modes.

Especially the **No pass through, computed from upstream cluster health** would be helpful. I am under the impression that this is a fairly standard configuration for production, and we plan to use this at Confluent.

Note that ClientTrafficPolicy would also need to support `cluster_min_healthy_percentages` xDS field in the [health check filter config](https://www.envoyproxy.io/docs/envoy/latest/api-v3/extensions/filters/http/health_check/v3/health_check.proto#envoy-v3-api-msg-extensions-filters-http-health-check-v3-healthcheck).

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.