gateway-api icon indicating copy to clipboard operation
gateway-api copied to clipboard
verified publisher icon kubernetes-sigs

Cross-Namespace HTTPRouteFilter type extensionRef

Open dorsegal opened this issue 5 months ago • 8 comments

What would you like to be added: I am using traefik to configure a middlewere once in the infra-ns. I would like this middlewere to be available in other namespaces for HTTPRouteFilter to use https://gateway-api.sigs.k8s.io/reference/spec/#httproutefilter According to spec extensionRef is LocalObjectReference which is bound to the same namespace

Why this is needed: https://gateway-api.sigs.k8s.io/guides/multiple-ns/?h=cros#cross-namespace-routing Since "Gateway API has core support for cross Namespace routing. This is useful when more than one user or team is sharing the underlying networking infrastructure, yet control and configuration must be segmented to minimize access and fault domains." It just make since to have some middleweres at infra level.

dorsegal avatar Jul 03 '25 19:07 dorsegal

I need this as well and I assume many traefik users that migrate to Gateway API require this feature. From code change perspective the changes are very trivial.

fgeck avatar Jul 14 '25 16:07 fgeck

Hello,

I'am really interested about this feature too.

@fgeck Please can you continue to work on this feature (https://github.com/kubernetes-sigs/gateway-api/pull/3916) ?

Thank you.

jgalais avatar Aug 24 '25 22:08 jgalais

This change would require a GEP to specify how the change will actually work; note that at a minimum, it will mean that the ExtensionReference middleware object being referenced would need a ReferenceGrant alongside it for the cross-namespace reference to be okay.

youngnick avatar Aug 25 '25 03:08 youngnick

I'm totally agree with you @youngnick, "ReferenceGrant" must be created also to validate the cross namespace mechanism.

What is the next step to help to implement this feature ?

jgalais avatar Aug 25 '25 07:08 jgalais

Hey @jgalais unfortunately I don't have sufficient capacity to implement the changes especially as I am completely new to contributing to the Kubernetes project

fgeck avatar Sep 12 '25 06:09 fgeck

The next steps for this would be to promote this to a GEP and push to have it included in a release. Note that this will require someone to put their hand up to do the work to push this forward, along with a shepherd. Keep an eye out for the new release process once we start kicking off the v1.5 release process soon.

youngnick avatar Sep 18 '25 01:09 youngnick

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Dec 17 '25 01:12 k8s-triage-robot

/remove-lifecycle stale

6ixfalls avatar Dec 17 '25 01:12 6ixfalls