<p>I am facing the following issue related specifying namespace quota.</p>
<ol>
<li>namespace quota specified is not getting created via helm.
My file namspacequota.yaml is as shown below</li>
</ol>
<pre><code>apiVersion: v1
kind: ResourceQuota
metadata:
  name: namespacequota
  namespace: {{ .Release.Namespace }}
spec:
  hard:
    requests.cpu: &quot;3&quot;
    requests.memory: 10Gi
    limits.cpu: &quot;6&quot;
    limits.memory: 12Gi
</code></pre>
<p>Below command used for installation</p>
<pre><code>helm install privachart3 . -n test-1
</code></pre>
<p>However the resourcequota is not getting created.</p>
<pre><code>kubectl get resourcequota -n test-1
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NAME                  CREATED AT
gke-resource-quotas   2021-01-20T06:14:16Z
</code></pre>
<ol start="2">
<li>I can define the resource-quota using the below kubectl command.</li>
</ol>
<p><code>kubectl apply -f namespacequota.yaml --namespace=test-1</code></p>
<p>The only change required in the file above is commenting of line number-5 that consist of release-name.</p>
<pre><code>kubectl get resourcequota -n test-1
NAME                   CREATED AT
gke-resource-quotas    2021-01-20T06:14:16Z
namespacequota         2021-01-23T07:30:27Z
</code></pre>
<p>However in this case, when i am trying to install the chart, the PVC is created, but the POD is not getting created.</p>
<p>The capacity is not an issue as i am just trying to create a single maria-db pod using &quot;Deployment&quot;.</p>
<p>Command used for install given below</p>
<pre><code>helm install chart3 . -n test-1
</code></pre>
<p>Output observed given below</p>
<pre><code>- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NAME: chart3
LAST DEPLOYED: Sat Jan 23 08:38:50 2021
NAMESPACE: test-1
STATUS: deployed
REVISION: 1
TEST SUITE: None
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
</code></pre>

George
<p>I got the answer from another the Git forum.
Upon setting a namespace quota we need to explicitly set the POD's resource.
In my case i just needed to specify the resource limit under the image.</p>
<pre><code>  - image: wordpress:4.8-apache
    resources:
      requests:
        memory: &quot;64Mi&quot;
        cpu: &quot;250m&quot;
      limits:
        memory: &quot;128Mi&quot;
        cpu: &quot;500m&quot;
</code></pre>
<p>Post that i am now able to observe the PODs as well</p>
<pre><code>[george@dis ]$ kubectl get resourcequota -n geo-test
NAME                  AGE   REQUEST                                                                                                                              LIMIT

gke-resource-quotas   31h   count/ingresses.extensions: 0/100, count/ingresses.networking.k8s.io: 0/100, count/jobs.batch: 0/5k, pods: 2/1500, services: 2/500   

namespace-quota       7s    requests.cpu: 500m/1, requests.memory: 128Mi/1Gi                                                                                     limits.cpu: 1/3, limits.memory: 256Mi/3Gi
[george@dis ]$ 
.



[george@dis ]$ kubectl get pod -n geo-test

NAME                                 READY     STATUS     RESTARTS     AGE

wordpress-7687695f98-w7m5b           1/1       Running     0           32s

wordpress-mysql-7ff55f869d-2w6zs     1/1       Running     0           32s

[george@dis ]$ 
</code></pre>
