Description of problem: - OCP 3.3 ResourceQuota doesn't support requests.storage Version-Release number of selected component (if applicable): - OCP 3.3 How reproducible: - 100% Steps to Reproduce: 1. Define ResourceQuota with requests.storage # cat c.yaml apiVersion: v1 kind: ResourceQuota metadata: name: storage-consumption spec: hard: requests.storage: "50Gi" 2. Create ResourceQuota # oc create -f c.yaml Actual results: --- # oc create -f c.yaml The ResourceQuota "storage-consumption" is invalid. * spec.hard[requests.storage]: Invalid value: "requests.storage": must be a standard resource type or fully qualified * spec.hard[requests.storage]: Invalid value: "requests.storage": must be a standard resource for quota Expected results: --- - Create resourceQuota with requests.storage as docs explains - https://docs.openshift.com/container-platform/3.3/dev_guide/compute_resources.html Additional info --- - We know that 3.4 or later works fine.
This is another doc error as well. OpenShift 3.3 only supported "persistentvolumeclaims", OpenShift 3.4 added support for requests.storage. Mike - can you fix 3.3 documentation to not include requests.storage or limits.storage?
Opened PR - https://github.com/openshift/openshift-docs/pull/4683
Derek, I know limits.storage is a doc issue, but could you please explain why 3.3 cannot implement requests.storage? Customers purchased and started using OpenShift after they expected that all of docs info could be feasible. Red Hat's "Not possible, so let's remove the feature from the doc" causes bad user experience.
Derek see https://bugzilla.redhat.com/show_bug.cgi?id=1466646#c3
Change is live. Closing. https://docs.openshift.com/container-platform/3.3/admin_guide/quota.html#managed-by-quota
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days