@ancient-wolf-19325 Is there workflow priority available now in flyte?

Workflow priority is not natively available as a first-class feature in Flyte's current public documentation or core APIs. However, there is ongoing discussion and some related work, such as supporting Kubernetes

priorityClassName

for Flyte pods, which helps prioritize Flyte system components at the Kubernetes level, but not user workflow executions directly. There is also mention of future plans for granular, priority-based scheduling in the Flyte roadmap, but this is not yet implemented for workflow executions themselves according to the available sources. If you are looking for user-level workflow priority (e.g., to influence scheduling order of workflow executions), this is not currently supported as a configurable parameter in Flyte's workflow or launch plan interfaces. Would you like more detail on current workarounds or the status of related features? Sources: - Flyte roadmap: Granular, priority-based scheduling 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.

provide some example @ancient-wolf-19325

It seems likely that Flyte does not currently support setting workflow execution priority directly via a user-facing parameter or API. The only related example in the data sources is setting Kubernetes

priorityClassName

for Flyte system pods, which is done at the infrastructure level and not per workflow execution. For example, you can configure Flyte pods (like FlytePropeller or FlyteConsole) to use a specific

priorityClassName

in their Kubernetes manifests to ensure they are less likely to be evicted under resource pressure, but this does not affect user workflow scheduling order (see example):

apiVersion: apps/v1
kind: Deployment
metadata:
  name: flytepropeller
spec:
  template:
    spec:
      priorityClassName: "system-cluster-critical"

For user workflows, there is no documented way to set a priority value that affects execution order. If you need to influence workflow scheduling, you may need to implement custom logic outside of Flyte or use Kubernetes-level controls. Would you like more detail on possible workarounds or how to use Kubernetes priorities for Flyte system components? Sources: - Support setting priorityClassName for flyte pods 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.