F

Flyte enables you to build & deploy data & ML pipelines, hassle-free. The infinitely scalable and flexible workflow orchestration platform that seamlessly unifies data, ML and analytics stacks. Explore and Join the Flyte Community!

Execution Quotas and Resource Management

Summary

The user is asking about enabling execution quotas with the resource manager and whether all quota namespaces must be declared at bootup, noting that this may not support dynamic properties such as per-user or per-workflow quotas. They believe that project-domain is the lowest level of granularity for setting resource quotas in this implementation.

Status
resolved
Tags
  • Quota
  • flyte
  • Dynamic Properties
  • User
  • Project-Domain
  • Question
  • Execution Quotas
  • Support Request
  • resource manager
  • Resource Management
  • Resource Manager
Source
#ask-the-community
    s

    sovietaced

    11/9/2024

    I guess its only good for limiting concurrency I guess too hmm

    s

    sovietaced

    11/8/2024

    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?