envoyproxy / envoyproxy/gateway

Support deployment of proxy without listeners

Open
#3,673 3 comments 0 reactions 0 assignees View on GitHub
area/infra-mgr stale
Dominant language
Go
Stars
3k
Forks
864
Avg merge
2d 2h
Merged PRs (30d)
140

Description

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

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.