refactor: align resource naming conventions with upstream CAPI

Signed-off-by: Andrew Rynhard <[email protected]>

Author: andrewrynhard

config/rbac/auth_proxy_role.yaml

@@ -1,7 +1,7 @@
 apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRole
 metadata:
-  name: controller-manager-proxy-role
+  name: proxy-role
 rules:
   - apiGroups: ['authentication.k8s.io']
     resources:

config/rbac/auth_proxy_role_binding.yaml

@@ -1,11 +1,11 @@
 apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRoleBinding
 metadata:
-  name: controller-manager-proxy-rolebinding
+  name: proxy-rolebinding
 roleRef:
   apiGroup: rbac.authorization.k8s.io
   kind: ClusterRole
-  name: controller-manager-proxy-role
+  name: proxy-role
 subjects:
   - kind: ServiceAccount
     name: default

config/rbac/leader_election_role.yaml

@@ -2,7 +2,7 @@
 apiVersion: rbac.authorization.k8s.io/v1
 kind: Role
 metadata:
-  name: controller-manager-leader-election-role
+  name: leader-election-role
 rules:
   - apiGroups:
       - ''

config/rbac/leader_election_role_binding.yaml

@@ -1,11 +1,11 @@
 apiVersion: rbac.authorization.k8s.io/v1
 kind: RoleBinding
 metadata:
-  name: controller-manager-leader-election-rolebinding
+  name: leader-election-rolebinding
 roleRef:
   apiGroup: rbac.authorization.k8s.io
   kind: Role
-  name: controller-manager-leader-election-role
+  name: leader-election-role
 subjects:
   - kind: ServiceAccount
     name: default