[k8s orch] Add option to specify separate service account for step pods #2688
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Describe changes
I implemented a new settings option to allow people to set a separate service account for the step pods that the kubernetes orchestrator spins up.
The motivation behind this is that some step code might need access to permissions in the cloud it is running on, say a Lambda function in AWS and such. In this scenario, it would help to provide a custom service account which is linked to an AWS IAM role with Lambda permissions on specific resources.
The way to achieve this currently involves setting the same service account for both the orchestrator and step pods but this means that:
Pre-requisites
Please ensure you have done the following:
develop
and the open PR is targetingdevelop
. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.Types of changes