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

InferencePool should have nested status #379

Closed
Tracked by #362
robscott opened this issue Feb 20, 2025 · 3 comments
Closed
Tracked by #362

InferencePool should have nested status #379

robscott opened this issue Feb 20, 2025 · 3 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@robscott
Copy link
Member

What happened:
In today's community meeting, @danehans pointed out that it's possible that multiple Gateways will be targeting the same InferencePool.

What you expected to happen:
We should really have a nested status that would allow different Gateways to put different status on InferencePool. This would be similar to Gateway API's RouteStatus.

@robscott robscott added the kind/bug Categorizes issue or PR as related to a bug. label Feb 20, 2025
@robscott
Copy link
Member Author

If anyone with access can add this to a v0.2 milestone, that would be appreciated.

/cc @kfswain @danehans

@ahg-g
Copy link
Contributor

ahg-g commented Feb 20, 2025

I assume this will require a v1alpha2 update? We also need to rename the port number in the ExtensionRef: #376

@kfswain
Copy link
Collaborator

kfswain commented Feb 21, 2025

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

3 participants