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 PoolObjectReferences #113

Open
danehans opened this issue Dec 19, 2024 · 2 comments
Open

Support Cross Namespace PoolObjectReferences #113

danehans opened this issue Dec 19, 2024 · 2 comments

Comments

@danehans
Copy link
Contributor

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
Copy link

enjoyliu commented Jan 6, 2025

I want to try it

@ahg-g
Copy link
Contributor

ahg-g commented Jan 6, 2025

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants