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.

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

Support Cross-Namespace Policy attachment #5143

Open
guydc opened this issue Jan 24, 2025 · 0 comments
Open

Support Cross-Namespace Policy attachment #5143

guydc opened this issue Jan 24, 2025 · 0 comments
Labels
area/api API-related issues area/policy

Comments

@guydc
Copy link
Contributor

guydc commented Jan 24, 2025

Description:

@dprotaso writes:

anyone know off hand if an EnvoyExtensionPolicy can match all HTTPRoutes.

I've tried an empty label selector
targetSelectors:

  • group: gateway.networking.k8s.io
    kind: HTTPRoute
    matchLabels: {} # Test all HTTPRoutes

[...]

I'm just trying to match all routes right now in the cluster. [...] I'm sidecaring an ext-proc server with the envoy proxy. But repeating the boilerplate config for each namespace is a bit much - do you recommend an alternative. I sorta consider this config as part of the 'gateway' deployment

GW-API currently only support Local Policy References in TargetRef(s).

To support scalable cross-namespace policy attachment, EG can introduce a NamespaceSelector as part of TargetSelectors (A custom EG policy selection mechanism), specifying which namespaces should be considered for policy attachment.

[optional Relevant Links:]

Any extra documentation required to understand the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/api API-related issues area/policy
Projects
None yet
Development

No branches or pull requests

1 participant