What's the best way to put a hard limit the number...
# ask-the-community
k
What's the best way to put a hard limit the number of pods that Flyte & SparkOperator will spin up? (let's say we have some vCPU limit of 100 or something)
k
Resourcequota
Flyte can also manage that
k
like this ?
Copy code
defaults:
    cpu: "1"
    memory: 150Mi
limits:
    cpu: "2"
    memory: 450Mi
project: flyteexamples
domain: development
k
No this is default cpu etc per task if unspecified and limits
k
Ah
this file for cluster resources
Copy code
attributes:
    projectQuotaCpu: "1000"
    projectQuotaMemory: 5TB
domain: development
project: flyteexamples
k
great thanks, just making sure that's the best way
k
Ya it should be and Flyte should start respecting it
There is some stuff that community is working on
122 Views