5 Commits (c8331835172c40d33f9841dfd6e9da469b11a7fa)

Author	SHA1	Message	Date
Derek Nola	664a98919b	Fix RBAC cloud-controller-manager name 3308 (#3388) ... * Changed cloud-controller-manager user name in ccm.yaml Signed-off-by: dereknola <derek.nola@suse.com> * Changed RBAC name in server.go Signed-off-by: dereknola <derek.nola@suse.com> * Changed "k3s" string prefix to version.Program to prevent static hardcoding Signed-off-by: dereknola <derek.nola@suse.com> * Changed user in ccm.yaml to k3s-cloud-controller-manager Signed-off-by: dereknola <derek.nola@suse.com>	4 years ago
Brad Davidson	58b5b21f0d	Don't pass cloud-provider flag to controller-manager ... As per documentation, the cloud-provider flag should not be passed to controller-manager when using cloud-controller. However, the legacy cloud-related controllers still need to be explicitly disabled to prevent errors from being logged. Fixing this also prevents controller-manager from creating the cloud-controller-manager service account that needed extra RBAC. Signed-off-by: Brad Davidson <brad.davidson@rancher.com>	4 years ago
Brad Davidson	31575e407a	Add Cluster ID support to k3s stub cloud controller ... Resolves warning 2 from #2471. As per https://github.com/kubernetes/cloud-provider/issues/12 the ClusterID requirement was never really followed through on, so the flag is probably going to be removed in the future. One side-effect of this is that the core k8s cloud-controller-manager also wants to watch nodes, and needs RBAC to do so. Signed-off-by: Brad Davidson <brad.davidson@rancher.com>	4 years ago
galal-hussein	07d4c1510d	Add lease permissions to ccm cluster role	5 years ago
galal-hussein	d2c1f66496	Add k3s cloud provider	5 years ago