#345 Propogate and calculate Queuing_Budget from CRD to task in Propeller Issue created by migueltol22 Motivation: Why do you think this is important? As part of #342, the CRD will contain the queuing_budget parameter. This value should be calculated at each node and passed down to the task. Goal: What should the final outcome look like, ideally? Queuing Budget is calculated at each node and propagated down to the task 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) • [x ] 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

#345 Propogate and calculate Queuing_Budget from CRD to task in Propeller Issue closed as not planned by github-actions[bot] flyteorg/flyte