-
Notifications
You must be signed in to change notification settings - Fork 52
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
Add support for feature gates #556
Comments
/assign hi @danielvegamyhre i'll try it |
Do we need to discuss which feature gates need to be added? |
/assign |
I have been thinking, can we include these two items in the feature gate? They can be enabled by default, and if there are more features in the future, they can be added. @danielvegamyhre |
I don't think we can (or should) put existing features behind feature gates, it would be weird for the feature gate to exist on some versions but not others. I think we should put new features (not released yet) which are somewhat risky behind a feature gate. Not sure off the top of my head if this aligns with upstream k8s standard practices, @kannon92 do you know? |
Understood. As far as I understand, the current features of JobSet are all existing ones, and there are no new unstable features yet. In that case, we can provide the feature gate functionality for other developers to use, but without any default configuration. How does that sound? @danielvegamyhre |
What would you like to be added:
Add support for feature gates in JobSet, like are used in upstream k8s and Kueue here.
Why is this needed:
The text was updated successfully, but these errors were encountered: