I have deployed flyte using flyte binary helm char...
# ask-the-community
a
I have deployed flyte using flyte binary helm chart. How can i configure project quotas? I tried using
Copy code
configuration:
  inline:
    cluster_resources:
      customData:
        - development:
            projectQuotaCpu: 
              value: "12"
            projectQuotaMemory:
              value: "20Gi"
        - production:
            projectQuotaCpu:
              value: "12"
            projectQuotaMemory:
              value: "20Gi"
        - staging:
            projectQuotaCpu:
              value: "12"
            projectQuotaMemory:
              value: "20Gi"
also tried using
flytectl update cluster-resource-attribute --attrFile cra.yaml
with no luck. when running a task that requests
Resources(cpu="5", mem="14Gi", gpu="1"),
i am getting below error
Copy code
requested resources exceed limits: [BackOffError] The operation was attempted but failed, caused by: pods "awlkglrkxzvpc5wrbsxn-testtestmmdetection-0" is forbidden: exceeded quota: project-quota, requested: limits.cpu=5,limits.memory=14Gi, used: limits.cpu=0,limits.memory=0, limited: limits.cpu=4,limits.memory=3000Mi
the configurations seems to be updated based on the result from
flytectl get cluster-resource-attribute -p flytesnacks -d development
Copy code
{
  "project": "flytesnacks",
  "domain": "development",
  "attributes": {
    "projectQuotaCpu": "12",
    "projectQuotaMemory": "20Gi"
  }
}
how can i address this?
d
I'm trying to reproduce this behavior but in the meantime, can you verify if there's a K8s ResourceQuota in your execution namespace?
kubectl get resourcequota -n <project-domain>
a
yes there is , but its not updated.
Copy code
NAME            AGE   REQUEST   LIMIT
project-quota   35h             limits.cpu: 0/4, limits.memory: 0/3000Mi
ok i manually edited the project-quota and it seems to be working now. Not sure why it was not updated earlier
thanks alot! @David Espejo (he/him)
d
yeah, any interesting logs from the flyte-binary pod? Not sure if using both the cra.yaml and the Helm spec somehow break things