New RunLLM response generated: >>>*# Question* Hi. I'm reading the documentation on enabling gang scheduling here: https://docs.flyte.org/en/latest/deployment/plugins/k8s/index.html I have question around enabling Yunikorn scheduler. In particular:

template:
  metadata:
    annotations:
      <http://yunikorn.apache.org/task-group-name|yunikorn.apache.org/task-group-name>: ""
      <http://yunikorn.apache.org/task-groups|yunikorn.apache.org/task-groups>: ""
      <http://yunikorn.apache.org/schedulingPolicyParameters|yunikorn.apache.org/schedulingPolicyParameters>: ""

Should the task-group-name be unique value shared for all the pods that belong to the same Flyte execution and task group? Or is there a different unique identifier that Yubikorn will pick to identify pods that belong to the same Flyte execution and task-group-name needs to be unique only within the specific Flyte execution. Cc @cool-lifeguard-49380 # Answer The

yunikorn.apache.org/task-group-name

annotation should be a unique value shared by all pods that belong to the same Flyte execution and task group. This ensures that Yunikorn can identify and group these pods together for scheduling purposes. According to the Flyte documentation, you need to set the

task-group-name

annotation to a unique value that is consistent across all pods in the same task group within a Flyte execution. This allows Yunikorn to recognize and manage these pods as a single entity for gang scheduling. Would you like more detail on this? Sources: - Flyte Documentation - Configure Kubernetes Plugins Slack Link https://flyte-org.slack.com/archives/CP2HDHKE1/p1719382144.027589 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.