Fix leader election rolebinding (#86)

Author: adriananeci

charts/cluster-registry-client/Chart.yaml

@@ -15,5 +15,5 @@ maintainers:
   - name: radu-catalina
     email: [email protected]
 
-version: 0.1.7
+version: 0.1.8
 appVersion: v1.4.2

charts/cluster-registry-client/README.md

@@ -1,6 +1,6 @@
 # cluster-registry-client
 
-![Version: 0.1.7](https://img.shields.io/badge/Version-0.1.7-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: v1.4.2](https://img.shields.io/badge/AppVersion-v1.4.2-informational?style=flat-square)
+![Version: 0.1.8](https://img.shields.io/badge/Version-0.1.8-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: v1.4.2](https://img.shields.io/badge/AppVersion-v1.4.2-informational?style=flat-square)
 
 Cluster Registry is a Rest API representing the source of record for all Kubernetes clusters in the infrastructure fleet. All clusters are automatically registered, and the information is accurately reflected in the Cluster Registry using a client-server architecture.
 

charts/cluster-registry-client/templates/rolebinding-leader-election.yaml

@@ -8,7 +8,7 @@ metadata:
 roleRef:
   apiGroup: rbac.authorization.k8s.io
   kind: Role
-  name: cluster-registry-leader-election-role
+  name: cluster-registry-leader-election
 subjects:
   - kind: ServiceAccount
     name: {{ include "cluster-registry-client.serviceAccountName" . }}