#201 Add the capability to limit 'how many resources' a user (namespace) can claim via dynamics nodes using k8s array plugin Issue created by DouglasCurbelo Motivation: Why do you think this is important? Currently, k8s array plugin does not enforce any control over the resources claimed by a particular user. This can lead to a single user claiming all available resources in the cluster. Goal: What should the final outcome look like, ideally? Ideally, we should be able to distribute available resources 'fairly' between users. At the bare minimum, we should be able to control the maximum number of resources used by a particular user. Incorporating the use of ResourceManager in the plugin can help us to enforce such limits (by requesting resource tokens to the manager before submitting pods to k8s) Flyte component ☐ Overall ☐ Flyte Setup and Installation scripts ☐ Flyte Documentation ☐ Flyte communication (slack/email etc) ☐ FlytePropeller ☐ FlyteIDL (Flyte specification language) ☐ Flytekit (Python SDK) ☐ FlyteAdmin (Control Plane service) ☑︎ FlytePlugins ☐ DataCatalog ☐ FlyteStdlib (common libraries) ☐ FlyteConsole (UI) ☐ Other [Optional] Propose: Link/Inline If you have ideas about the implementation please propose the change. If inline keep it short, if larger then you link to an external document. Additional context Add any other context or screenshots about the feature request here. Is this a blocker for you to adopt Flyte Please let us know if this makes it impossible to adopt Flyte flyteorg/flyte

#201 Add the capability to limit 'how many resources' a user (namespace) can claim via dynamics nodes using k8s array plugin Issue closed as not planned by github-actions[bot] flyteorg/flyte