Description
/kind bug
What happened: I installed the cloud controler manager into my cluster during bootstrap using the manifests from this repository. After bootstrapping I wanted to apply the helm chart (to modify some values, especially the cluster name). But this is not possible since the manifest's daemonset uses the label "k8s-app" in the spec and the helm chart uses labels "component", "app" and "release". That way Kubernetes refuses to update the daemonset.
What you expected to happen: The initially installed daemonset should be updated when the helm chart is applied
How to reproduce it: See what happened
Anything else we need to know?: It would be nice to be able to apply the chart after initial installation via the manifests. Including the release in the match labels makes this nearly impossible
Environment:
- openstack-cloud-controller-manager(or other related binary) version: v1.32.0
- OpenStack version: N/A
- Others: N/A