Please add support for serviceAccountName

[jeffgus]

I can't find a way to assign a serviceAccount for the pods to use. This is important, not only for using SCC in Openshift (allow anyuid, etc), but also for using the serviceAccount with IRSA (https://aws.amazon.com/blogs/containers/fine-grained-iam-roles-for-red-hat-openshift-service-on-aws-rosa-workloads-with-sts/). If I can map a serviceAccount to the Pod (via the StatefulSet), then I can grant access to that SA to things like S3 buckets via the AWS role.

Currently, I can't even start the pod because the Operator makes SSC mad. This is a non-starter:

create Pod node-0 in StatefulSet node failed error: pods "node-0" is forbidden: unable to validate against any security context constraint: [provider "anyuid": Forbidden: not usable by user or serviceaccount, provider "pipelines-scc"

[pengzhouml]

Thanks for the feedback. We are actually working on adding the service account right now. I should be added in the next release.