Bug with k3k-node-proxy ClusterRole

[enrichman]

The k3k-node-proxy ClusterRole is needed from the Kubelet to list the host nodes, and fetch some metrics.

The chart is currently building the name with the release installation. But the kubelet is expecting a fixed name for the ClusterRoleBinding, such as k3k-node-proxy. This means that if installing the chart with a different name than k3k will result in some permissions error.

k3k/charts/k3k/templates/rbac.yaml

Lines 30 to 37 in c285004

	kind: ClusterRoleBinding
	apiVersion: rbac.authorization.k8s.io/v1
	metadata:
	name: {{ include "k3k.fullname" . }}-node-proxy
	roleRef:
	kind: ClusterRole
	name: {{ include "k3k.fullname" . }}-node-proxy
	apiGroup: rbac.authorization.k8s.io

k3k/pkg/controller/cluster/cluster.go

Lines 317 to 320 in c285004

	clusterRoleBinding := &rbacv1.ClusterRoleBinding{}
	if err := c.Client.Get(ctx, types.NamespacedName{Name: "k3k-node-proxy"}, clusterRoleBinding); err != nil {
	return fmt.Errorf("failed to get or find k3k-node-proxy ClusterRoleBinding: %w", err)
	}