Use real ServiceAccount instead of `default` - Githubissues

kubernetes-sigs / cluster-api-operator

Home for Cluster API Operator, a subproject of sig-cluster-lifecycle

https://cluster-api-operator.sigs.k8s.io

Apache License 2.0

146 stars 60 forks source link

Use real ServiceAccount instead of `default` #518

Closed cwrau closed 1 week ago

cwrau commented 1 month ago

What steps did you take and what happened: I tried installing the chart, failing at our policy to not use the default ServiceAccount

What did you expect to happen: That the chart would create it's own ServiceAccount for the operator.

Anything else you would like to add: It is best-practice to create specific ServiceAccounts for each component.

Environment:

Cluster-api-operator version: latest
Cluster-api version: N/A
Minikube/KIND version: N/A
Kubernetes version: (use kubectl version): N/A
OS (e.g. from /etc/os-release): N/A

/kind bug [One or more /area label. See https://github.com/kubernetes-sigs/cluster-api-operator/labels?q=area for the list of labels]

k8s-ci-robot commented 1 month ago

This issue is currently awaiting triage.

If CAPI Operator contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.