Skip to content

Standardized usage for Envoy Gateway #10

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.

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

Closed
Xunzhuo opened this issue Sep 29, 2024 · 1 comment · Fixed by #18
Closed

Standardized usage for Envoy Gateway #10

Xunzhuo opened this issue Sep 29, 2024 · 1 comment · Fixed by #18
Assignees

Comments

@Xunzhuo
Copy link
Member

Xunzhuo commented Sep 29, 2024

Currently we use EnvoyProxy CR to manually patch the boostrap to add external processing filter, add original_destination_cluster for envoyproxy. This is not a recommended approach to use eg and gateway api, and this is very static and hard to maintain, and breaks the design of gateway-api concepts.

We should standardize to use eg and gateway api by:

  1. Use EnvoyExtensionPolicy CRD to dynamically set up external processing filter for gateway listener.
  2. Use EnvoyPatchPolicy CRD or implement extension hook server to add original_destination_cluster.
  3. Remove envoyproxy CRD, to prevent manually patching the bootstrap.

/assign

@Xunzhuo Xunzhuo changed the title Using EnvoyExtensionPolicy for External Processing Standardized usage for Envoy Gateway Sep 29, 2024
@smarterclayton
Copy link
Contributor

/assign @kfswain

@kfswain kfswain mentioned this issue Oct 14, 2024
shaneutt pushed a commit to shaneutt/gateway-api-inference-extension that referenced this issue Apr 17, 2025
…e-builds

fix: basic container image builds for linux
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants