-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
CNV#29984: Document auto setting of mem and CPU resource limits #75865
Conversation
@danielclowers: all tests passed! Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
/lgtm |
/label peer-review-needed |
@@ -8,5 +8,6 @@ | |||
|
|||
A _resource quota_, defined by the `ResourceQuota` object, imposes restrictions on a namespace that limit the total amount of compute resources that can be consumed by resources within that namespace. | |||
|
|||
The `HyperConverged` custom resource (CR) defines the user configuration for the Containerized Data Importer (CDI). The CPU and memory request and limit values are set to a default value of `0`. | |||
This ensures that pods created by CDI that do not specify compute resource requirements are given the default values and are allowed to run in a namespace that is restricted with a quota. | |||
The `HyperConverged` custom resource (CR) defines the user configuration for the Containerized Data Importer (CDI). The CPU and memory request and limit values are set to a default value of `0`. This ensures that pods created by CDI that do not specify compute resource requirements are given the default values and are allowed to run in a namespace that is restricted with a quota. |
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.
With or without an article? You use both; might want parallelism?
The `HyperConverged` custom resource (CR) defines the user configuration for the Containerized Data Importer (CDI). The CPU and memory request and limit values are set to a default value of `0`. This ensures that pods created by CDI that do not specify compute resource requirements are given the default values and are allowed to run in a namespace that is restricted with a quota. | |
The `HyperConverged` custom resource (CR) defines the user configuration for the Containerized Data Importer (CDI). The CPU and memory request and limit values are set to a default value of `0`. This ensures that pods created by the CDI that do not specify compute resource requirements are given the default values and are allowed to run in a namespace that is restricted with a quota. |
One nit. Gj! |
CNV#29984: Document auto setting of mem and CPU resource limits
/cherry-pick enterprise-4.16 |
@stevsmit: new pull request created: #76369 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
CNV#29984: Document auto setting of mem and CPU resource limits
CNV#29984: Document auto setting of mem and CPU resource limits
CNV#29984: Document auto setting of mem and CPU resource limits
Version(s):
4.16
Issue:
https://issues.redhat.com/browse/CNV-29984
Link to docs preview:
https://75865--ocpdocs-pr.netlify.app/openshift-enterprise/latest/virt/storage/virt-configuring-cdi-for-namespace-resourcequota.html#virt-about-cpu-and-memory-quota-namespace_virt-configuring-cdi-for-namespace-resourcequota
QE review:
Additional information: