New RunLLM response generated: >>>*# Question* Hello. We're looking to enable some quotas for executions so I'm looking at the resource manager. It looks like the resource manager design forces you to declare all the possible quota namespaces (ie. rate limiting keys) during bootup but this doesn't really support the ability to have a quota on dynamic properties like a per-user basis or a per-workflow basis. Is this understanding correct? # Answer Yes, your understanding is correct. According to the Flyte ResourceManager documentation, the ResourceManager requires predefined resource pools, which means that dynamic properties like per-user or per-workflow quotas are not inherently supported. The ResourceManager is designed to manage resource allocations based on predefined configurations, and it uses tokens to represent resource units. Would you like more detail on how to potentially work around this limitation? Sources: - Flyte ResourceManager documentation Slack Link https://.slack.com/archives/CP2HDHKE1/p1731105388.916929 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.