-
Notifications
You must be signed in to change notification settings - Fork 0
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
Make per-namespace Quotas configurable #16
Comments
@blairdrummond My thought for the easiest implementation was to use a label on the (reason for a label over an annotation is we could do filters in the future to see what profiles have overridden limits) |
@rohank07
When the profile is created, the default quotas are applied and the the labels included in the profile.jsonnet are also added/override those affected defaults. Storage label name: All that would then be required would be to add |
As per this: https://www.youtube.com/watch?v=KUyEuY5ZSqI&t=653s
It would make sense for the metadata to be stored within the Profile metadata? Maybe?
The exact location of the metadata isn't super important, as long as it cannot be modified by users. We should decide on and implement this, incorporating it with the design of
aaw-kubeflow-profiles
to keep the quotas in CI.The text was updated successfully, but these errors were encountered: