You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
The "Ready" condition adds unnecessary overhead for Gateway controllers and goes against Gateway API's decision to avoid a "Ready" condition. We should remove it until we have a very clear definition and use case for it.
What you expected to happen:
We really don't want to require controllers to constantly update "Ready" status on InferencePool based on the readiness of underlying Pods. We've intentionally avoided a "Ready" condition in Gateway API, and I'd recommend leaving it out of this release until we can have a clearer definition and consensus around this.
The text was updated successfully, but these errors were encountered:
What happened:
The "Ready" condition adds unnecessary overhead for Gateway controllers and goes against Gateway API's decision to avoid a "Ready" condition. We should remove it until we have a very clear definition and use case for it.
What you expected to happen:
We really don't want to require controllers to constantly update "Ready" status on InferencePool based on the readiness of underlying Pods. We've intentionally avoided a "Ready" condition in Gateway API, and I'd recommend leaving it out of this release until we can have a clearer definition and consensus around this.
The text was updated successfully, but these errors were encountered: