Consider Adding Egress Proxy Support

[danehans]

The project is currently targeting the edge reverse proxy use case. Should the project also support forward proxy, e.g. egress?

[mattklein123]

+1. P1 feature though imo.

[youngnick]

There has been some upstream discussion in Gateway API community meetings about egress, there's an empty tracking issue at kubernetes-sigs/gateway-api#1011.

I think there's pretty significant design challenges around how to make the lower-level networking work for egress in a generic way though.

[LukeShu]

I think this would be an exciting feature to add, but IMO it adds too much technical scope for us to actually think about implementing right now. Keep it in mind, and perhaps keep an eye on Gateway API's treatment of egress and give feedback on it. But not something to actually think about implementing in the near-term.

[LukeShu]

To say it more explicitly: While I think this is something we should consider for the future, I oppose adding it to GOALS.md.

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.