Add podServiceAccountName to SpinApp CRD
With this PR, users are able to specify the ServiceAccountName for underlying pods
closes #226
What does the failure scenario look like when a service account with the provided name doesn't exist?
@michelleN that's a good question. When a user tries to create a Pod and is referencing a non-existing ServiceAccountName, the Pod is not accepted at all and a corresponding error message is presented to the user.
I would prefer our controller also checking for the specified ServiceAccountName in the current namespace, before it starts with creating underlying Kubernetes primitives
Any tips how I could implement validation of the serviceAccountName in the controller in order to prevent the SpinApp from being created, if the user provides a non-existing serviceAccountName?