✨ Add serviceAccountName to DeploymentSpec

[steve-fraser]

What this PR does / why we need it:

Today, it's difficult to override the service account with an IRSA configured value. I would like the ability override the serviceAccountName for the deployment

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

[k8s-ci-robot]

Welcome @steve-fraser!

It looks like this is your first PR to kubernetes-sigs/cluster-api-operator 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/cluster-api-operator has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @steve-fraser. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[Fedosin]

/ok-to-test

[steve-fraser]

/retest

[steve-fraser]

/retest

[steve-fraser]

/retest

[steve-fraser]

/retest

[steve-fraser]

/retest

[steve-fraser]

/retest

[Fedosin]

Fix for the linter issue: #176

[steve-fraser]

/retest

[furkatgofurov7]

/lgtm

[furkatgofurov7]

@steve-fraser thanks for the PR. Can you please squash your commits, otherwise LGTM.
/lgtm cancel
/hold lgtm pending squash

[alexander-demicev]

Thanks for the PR, we can merge it after commits are squashed.

[furkatgofurov7]

Thanks @steve-fraser!

/lgtm
/cc @alexander-demicev for approval

[k8s-ci-robot]

@furkatgofurov7: GitHub didn't allow me to request PR reviews from the following users: for, approval.

Note that only kubernetes-sigs members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

Thanks @steve-fraser!

/lgtm
/cc @alexander-demicev for approval

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: d0c562f8e23c9fa1b63694057809288a6d235db1

[furkatgofurov7]

/assign @alexander-demicev

for approval

[furkatgofurov7]

/hold cancel

[alexander-demicev]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alexander-demicev

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [alexander-demicev]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment