envoyproxy / envoyproxy/gateway

Support deployment of proxy without listeners

Offen
#3,673 3 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
area/infra-mgr stale
Vorherrschende Sprache
Go
Sterne
3k
Forks
864
Ø Merge
2 T. 2 Std.
Gemergte PRs (30 T.)
140

Beschreibung

*Description*:
When using merge-gateways, the proxy can be eagerly deployed based on the gatewayclass, before any gateway is available. This is useful for users that want to ensure that the proxy is successfully deployed and discover LB addresses prior to configuring the proxy with resources like `Gateway`, `xRoute`, etc.

However, since a service without ports cannot be created, this functionality is currently disabled: https://github.com/envoyproxy/gateway/issues/3044.

Some options to consider:
- Render the service conditionally, only if listeners (ports) exist. Other resources (deployment, etc.) can still be provisioned.
- Allow EnvoyProxy to explicitly define "default" service ports (e.g. 80, 443). The default target will be overriden once a listener exists. This can either be a proper API (preferred) or work through a patch mechanism.

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.