Support Cross Namespace PoolObjectReferences

[danehans]

Since InferencePool and InferenceModel resources are managed by different personas they may reside in different namespaces. Therefore, PoolObjectReference should support an optional namespace field that defines the namespace of the referenced object. When this field is unspecified or specifies the same namespace as the InferencePool, the referenced object must be in the same namespace as the InferencePool. When namespace specifies a different namespace from the InferencePool, a ReferenceGrant object is required in the referenced object's namespace to allow the reference.

[enjoyliu]

I want to try it

[ahg-g]

I discussed this with @robscott briefly in the initial API proposal and we opted to start without allowing cross namespace referencing of resources to avoid dealing with that complexity and not to have dependencies on the upstream gateway apis initially. @robscott wdyt?

With ReferenceGrant, is it the extension itself that needs to honor the policy?

[danehans]

+1 on not supporting this issue for now but let's keep it open to track interest.

[danehans]

xref #149 (comment) from @liu-cong

[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