[earthscope, staging] Add test quota policy config#7921
Open
jnywong wants to merge 1 commit into2i2c-org:mainfrom
Open
[earthscope, staging] Add test quota policy config#7921jnywong wants to merge 1 commit into2i2c-org:mainfrom
jnywong wants to merge 1 commit into2i2c-org:mainfrom
Conversation
Contributor
|
Merging this PR will trigger the following deployment actions. Support deploymentsNo support upgrades will be triggered Staging deployments
Production deployments
|
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
This is a sample PR to demonstrate how to apply a quota policy of "250 GiB-hours1 of memory requests over 7 days to user group
cpu-1". The user group is derived from the scopes requested from OIDC.See docs on how to configure quota policies in general.
Ref #7909
Footnotes
I chose this example value because I can see one user on the staging hub with a current memory request usage of 236 GiB-hours in the last 7 days (as of writing on Friday 13th March). ↩