Usually application owner or project owner will specify the quota settings (Memory and CPU) during project creation. But sometimes, they realize that the requested resource is not enough to run their applications.
Usually we name the quota with its specifications and not a good idea to edit this existing quota. Standard practice is to remove/delete the quota for the project and recreate new quota with new values.
Note : You must set quota together with limit.
Check current quota
# oc get quota -n myproject
NAME AGE
proj-quota-8gi 284d
# oc describe quota proj-quota-8gi -n myproject
Name: proj-quota-8gi
Namespace: myproject
Resource Used Hard
-------- ---- ----
requests.cpu 4726m 5400m
requests.memory 7000Mi 8Gi
Delete the Quota
WARNING : mention project namespace to avoid any accidental quota delete.
# oc delete quota proj-quota-32gi -n myproject
Create new Quota Template
This is the template file where we mention the memory and CPU quota details.
# cat proj-quota-32Gi_no_limit.yaml
apiVersion: v1
kind: ResourceQuota
metadata:
creationTimestamp: null
name: proj-quota-32gi
spec:
hard:
requests.cpu: 19200m
requests.memory: 32Gi
Create new Quota from Template
# oc create -f proj-quota-32Gi_no_limit.yaml -n PROJECT_NAME
Verify new Quota
# oc get quota -n myproject
NAME AGE
proj-quota-32gi 1d
# oc describe quota proj-quota-32gi -n myproject
Name: proj-quota-32gi
Namespace: myproject
Resource Used Hard
-------- ---- ----
requests.cpu 5513m 19200m
requests.memory 10724Mi 32Gi
]# oc describe project myproject |grep Quota -A5
Quota:
Name: proj-quota-32gi
Resource Used Hard
-------- ---- ----
requests.cpu 5513m 19200m
requests.memory 10724Mi 32Gi
That’s it.