<#5575 [Core feature] Updating annotations of pods...
# flyte-github
c
#5575 [Core feature] Updating annotations of pods belonging Ray cluster in order to adopting Yunikorn Gang scheduling Issue created by 0yukali0 ### Motivation: Why do you think this is important? Implementing mechanism eases user overhead about updating annotations and is ability to give different task group name for head pod and each work groups to monitor each groups status with yunikorn gang scheduling . ### Goal: What should the final outcome look like, ideally? Annotations of pod belonging head group
Copy code
yunikorn.apache.org/schedulingPolicyParameters: “placeholderTimeoutSeconds=30”
yunikorn.apache.org/taskGroupName: “taskgroup-raycluster-head”
yunikorn.apache.org/taskGroup: “
    TaskGroups: [
      {
        name: taskgroup-raycluster-head
        minMember: 1
        minResource: {
          cpu: 1,
          memory: 500Mi,
        },
        nodeSelector: ...,
        tolerations: ...,
        affinity: ...,
      },
      {
        name: taskgroup-raycluster-worker-0
        minMember: 5
        minResource: {
          cpu: 2,
          memory: 1Gi,
        },
        {
        name: taskgroup-raycluster-worker-1
        minMember: 5
        minResource: {
          cpu: 2,
          memory: 1Gi,
        },
      },
    ]
    "
Pods of worker group 0
name: taskgroup-raycluster-worker-0
Pods of worker group 1
name: taskgroup-raycluster-worker-1
### Describe alternatives you've considered A mechanism updates annotations for pods according to the group they belongs. Available solution to activate yunikorn gang scheduling via defining pod template results in all pods sharing same task group name, resource and parameters annotations. In order to distinguish task groups between head and workers, ray plugin updating annotations including task group name, resource and parameters to a ray pod based on its role when creating ray cluster, When user set "batch-scheduler" with "yunikorn", ray plugin is going to generate separate task group name for each pod, resource of placeholders and parameters. Head pod annotations have task group names, placeholders' resource and parameters. Meanwhile, pods belonging worker group has task group name generated from their worker group. ### Propose: Link/Inline OR Additional context No response ### Are you sure this issue hasn't been raised already? • Yes ### Have you read the Code of Conduct? • Yes flyteorg/flyte