You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[release-1.27] [occm] Use standard service account name in OCCM helm chart (kubernetes#2448)
* Use standard service account name in OCCM helm chart (kubernetes#2332)
This removes the `openstack-` prefix from the service account name
used by the cloud-controller-manager and moves the default values into
the values file.
The change is motivated by the following:
- Create suitable service accounts, cluster roles and cluster role
bindings for use with `--use-service-accounts-credentials=true`
- Normalise service account names in the helm chart and plain
manifests
- Adhere to naming conventions across external cloud controller
managers for different clouds (e.g. AWS, GCP, ...)
Specifically the first point deserves further details. Prior to this
change, users who install the cloud controller manager with helm,
would run into the following error when creating load balancers:
```
E0818 08:27:33.802407 11 controller.go:291] error processing service default/hello-bug (will retry): failed to ensure load balancer: failed to patch service object default/hello-bug: services "hello-bug" is forbidden: User "system:serviceaccount:kube-system:cloud-controller-manager" cannot patch resource "services" in API group "" in the namespace "default"
```
Which is due to the fact that the controller is running with the
`cloud-controller-manager` service account because
`--use-service-account-credentials` is set to `true` by default and
the client is initialised with:
```
clientset := clientBuilder.ClientOrDie("cloud-controller-manager")
```
Whilst users can work around this by passing
`--use-service-account-credentials=false`, the desired behaviour would
be to install suitable RBAC in the first place.
See:
- https://kubernetes.io/docs/concepts/architecture/cloud-controller/
- https://kubernetes.io/docs/tasks/administer-cluster/running-cloud-controller/
- kubernetes#2049
- kubernetes#1722
- kubernetes#1755
Signed-off-by: Wolodja Wentland <[email protected]>
* Remove spurious whitespace in OCCM values file (kubernetes#2347)
The space character was sadly introduced in an earlier PR and had not
been picked up by the helm linter, presumably because the GHA did
not run.
Signed-off-by: Wolodja Wentland <[email protected]>
---------
Signed-off-by: Wolodja Wentland <[email protected]>
Signed-off-by: Wolodja Wentland <[email protected]>
0 commit comments