#343 Cost Optimizations - Quality Of Service and Config Issue created by migueltol22 Motivation: Why do you think this is important? As part of #342, we would like a user to be able to specify a Quality of Service Level for the workflow which corresponds to a value that will be used for queuing the workflow. Goal: What should the final outcome look like, ideally? A user specifies a quality of service parameter in their workflow that corresponds to a value that is part of the config set in Flyte Admin

@workflow_class(quality_of_service=0):

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. Flyte component ☐ Overall ☐ Flyte Setup and Installation scripts ☐ Flyte Documentation ☐ Flyte communication (slack/email etc) ☐ FlytePropeller • [x ] FlyteIDL (Flyte specification language) • [ x] Flytekit (Python SDK) • [ x] FlyteAdmin (Control Plane service) ☐ FlytePlugins ☐ DataCatalog ☐ FlyteStdlib (common libraries) ☐ FlyteConsole (UI) ☐ Other [Optional] Propose: Link/Inline Change in idl and flytekit to add support for quality of service. In FlyteAdmin these values will correspond to a time interval as part of flyteadmin config. Something like

0: no queuing,
1: 30 mins,
2: 2 hours

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