<#6514 Set service account in base ray pod spec, a...
# flyte-github
c
#6514 Set service account in base ray pod spec, allow it to be overriden by pod template Pull request opened by Sovietaced ## Tracking issue Closes #6513 ## Why are the changes needed? It is impossible to customize the ray head/worker node service account names beyond the global config option. ## What changes were proposed in this pull request? Instead of overwriting the service accounts in the head/worker pod specs after they have been rendered this pull request moves the logic to set the configured service account to the base pod spec. The base pod spec is the foundation for the head/worker pod spec. If the head/worker pod templates don't configure a service account the head/worker service account will remain the same, otherwise it allows the pod templates to customize the service account name. This should still respect the semantics desired in #5928 ## How was this patch tested? Tested in our production environment. ## Check all the applicable boxes • I updated the documentation accordingly. • All new and existing tests passed. • All commits are signed-off. ## Related PRs ## Docs link https://bito.ai#summarystart| ### Summary by Bito This pull request enhances the customization of service account names for ray head and worker nodes by moving the logic to the base pod specification. It allows pod templates to override the service account name while maintaining default behavior when not specified, improving flexibility and respecting existing configurations. flyteorg/flyte