#3898 [Core feature] Custom K8s SA parameters in the Ray plugin Issue created by aybidi Motivation: Why do you think this is important? The Ray plugin creates the RayCluster with the default K8s SA, which may not have permission to access other Flyte resources. The solution to this one maybe similar to #3886 , which requests making

Namespace

a user-configurable parameter. Maybe we can combine both the issue and suggest one -- allowing users to customize more fields in the RayJob (and RayCluster) CR being created by the backend plugin. Goal: What should the final outcome look like, ideally? Users can provide custom K8s SA parameters on the

flytekite

side. Describe alternatives you've considered n/a 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