envoyproxy / envoyproxy/gateway

Support deployment of proxy without listeners

Aperta
#3,673 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub
area/infra-mgr stale
Lingua principale
Go
Stelle
3k
Fork
864
Merge medio
2g 2h
PR unite (30g)
140

Descrizione

*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.

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.