New RunLLM response generated: >>>*# Question* Regarding Task Resource we found it unclear what the evaluation order is for defaults and limits # Answer The evaluation order for task resource defaults and limits in Flyte is as follows: 1. Task Definition: If a task specifies its own resource requests and limits, these values take precedence. 2. Project-Domain Customization: If no specific values are set in the task definition, Flyte checks for any custom resource configurations set for the project-domain combination using

flytectl

. 3. Global Defaults: If neither the task definition nor project-domain customization provides resource values, the global default values specified in the FlyteAdmin configuration (

task_resource_defaults.yaml

) are used. According to the Flyte documentation, default values get injected as the task requests and limits when a task definition omits a specific resource. Limit values are only used for validation, ensuring that neither a task request nor limit can exceed the configured limits. Would you like more detail on any specific part of this evaluation order? Sources: - Flyte Documentation on Customizable Resources Slack Link https://.slack.com/archives/CP2HDHKE1/p1727110479.659159 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.