Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Evaluate mergedGateways in envoy-gateway #3811

Open
Tracked by #3150
mcharriere opened this issue Jan 6, 2025 · 0 comments
Open
Tracked by #3150

Evaluate mergedGateways in envoy-gateway #3811

mcharriere opened this issue Jan 6, 2025 · 0 comments
Labels
component/gateway-api epic/gatewayapi team/cabbage Team Cabbage

Comments

@mcharriere
Copy link

mcharriere commented Jan 6, 2025 •
edited
Loading

Explore and understand this deployment mode offered by the envoy-gateway.

Consider:

  • security risks
  • configuration merge strategies across several Gateways
  • global configuration in GatewayClass
  • Listener conflict resolution

Unfortunately the mergedGateways feature is not standardized and each implementations is doing differently (or not at all).

We need to understand if this is suitable for customers and production use.
@github-project-automation github-project-automation bot moved this to Inbox 📥 in Roadmap Jan 6, 2025
@mcharriere mcharriere mentioned this issue Jan 6, 2025
Open
@weatherhog weatherhog moved this from Inbox 📥 to Backlog 📦 in Roadmap Jan 9, 2025
@teemow teemow moved this from Backlog 📦 to Inbox 📥 in Roadmap Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component/gateway-api epic/gatewayapi team/cabbage Team Cabbage
Projects
Roadmap
Status: Inbox 📥
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mcharriere