Add CEL Validation when HTTPRoute for InferencePool BackendRef when the Port is set

[rahulgurnani]

What happened:

Add CEL validation for HTTPRoute.BackendRef.Port is set and an InferencePool is targeted to catch case mentioned in discussion here

What you expected to happen:

The validation should catch the scenario discussed here

How to reproduce it (as minimally and precisely as possible):

Following the docs for inference gateway: https://gateway-api-inference-extension.sigs.k8s.io/ with Port set in HttpRoute succeeds.

Anything else we need to know?:

[rahulgurnani]

/assign

[youngnick]

I don't think it's really valid to add handling for InferencePool inside upstream Gateway API - InferencePool is an extension, should we be allowing extensions to add code to the upstream?

[k8s-triage-robot]

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