gateway-api icon indicating copy to clipboard operation
gateway-api copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

BackendObjectReference port should be compatible with named port

Open davinkevin opened this issue 2 years ago • 7 comments

What would you like to be added: BackendObjectReference port should be compatible with named port

Why this is needed:

As user of the Gateway API, I'm forced to use the port number defined by the backend service. However, this port may change and I have to sync this manually and/or automate a check for it.

In Ingress API, we have a specific API, where the backend.service.port.name can be used to avoid a direct relationship to a port. This port.name is a useful indirection allowing to separate the implementation (port.number) from the purpose (port.name).

With the GatewayAPI, we don't have this concept anymore.

davinkevin avatar Sep 23 '23 13:09 davinkevin

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 Jan 30 '24 01:01 k8s-triage-robot

/unstale 😇

davinkevin avatar Jan 31 '24 09:01 davinkevin

The Kubernetes project currently lacks enough active 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 rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle rotten

k8s-triage-robot avatar Mar 01 '24 10:03 k8s-triage-robot

@shaneutt, is it possible to remove the lifecycle for it, please?

davinkevin avatar Mar 01 '24 10:03 davinkevin

Yes, albeit nobody has stepped up to drive it forward, it's still technically in triage so we need to check on it still.

shaneutt avatar Mar 01 '24 13:03 shaneutt

For the record, this was an intentional omission of the API. Supporting named ports adds more complexity for both implementers and users and generally just introduces more ways that things can break. For anyone interested in pushing this forward, you would need to show that the value of providing this option outweighed the complexity it introduces.

robscott avatar Mar 06 '24 23:03 robscott

I worked on that for few weeks and I understand the reasoning.

Feel free to close it, at least we have an issue answering this question for future people doing the same migration as me… and using a lot named port.

davinkevin avatar Apr 25 '24 06:04 davinkevin

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 Jul 24 '24 07:07 k8s-triage-robot