-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
explain multi-project quota #2596
Conversation
=== Selecting Projects | ||
|
||
Projects can be selected based on either annotation selection, label selection, or both. | ||
For example, `oc create clusterquota for-user --project-annotation-selector openshift.io/requester=deads --hard pods=10 --hard secrets=20` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
your name will live in docs forever :-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We tend to use generic user names, so I am going to unfortunately be a killjoy and recommend replacing instances of "deads" with a replaceable:
<user-name>
😿
@adellape @ahardin-rh Is there a tag I should use for 3.3 items? I've got a few doc pulls that should go in. |
to be shared across multiple projects. Resources used in each selected project | ||
will be aggregated and that aggregate will be used to limit resources across | ||
all the selected projects. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to add an anchor just above the heading:
[[multi-project-quotas-selecting-projects]]
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to add an anchor just above the heading:
[[multi-project-quotas-selecting-projects]]
done
@deads2k I applied labels/milestone for forthcoming 3.3 and added a few comments. Cheers! 🍻 |
comments addressed. |
@deads2k Thanks! |
[rev_history] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
two comments, then lgtm
Because of the locking consideration when claiming quota allocations, the | ||
number of active projects selected by a multi-project quota is an important consideration. | ||
Selecting more than 100 projects under a single multi-project quota may have | ||
deleterious effects on API server responsiveness in those projects. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
deterious?
|
||
A project-admin is not allowed to create or modify the multi-project quota that limits | ||
him, but he is allowed to view the multi-project quota documents are applied to his project. | ||
He can do this via the `*AppliedClusterResourceQuota*` resource. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
write doc gender neutral
Adds documentation that explains how to use https://trello.com/c/qJUVjQnj/713-13-multi-project-quota