kubernetes/cluster/addons/cloud-controller-manager/cloud-node-controller-binding.yaml

apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
  labels:
    addonmanager.kubernetes.io/mode: Reconcile
  name: system::leader-locking-cloud-controller-manager
  namespace: kube-system
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: system::leader-locking-cloud-controller-manager
subjects:
- kind: ServiceAccount
  name: cloud-controller-manager
  namespace: kube-system
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  labels:
    addonmanager.kubernetes.io/mode: Reconcile
  name: system:cloud-controller-manager
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: system:cloud-controller-manager
subjects:
- kind: User
  apiGroup: rbac.authorization.k8s.io
  name: system:cloud-controller-manager
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  labels:
    addonmanager.kubernetes.io/mode: Reconcile
  name: system:controller:cloud-node-controller
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: system:controller:cloud-node-controller
subjects:
- kind: ServiceAccount
  name: cloud-node-controller
  namespace: kube-system
Turn on CCM in kube-up when cloudprovider=external Currently if we disable cloud provider by the following CLOUD_PROVIDER_FLAG=external KUBE_FEATURE_GATES=DisableCloudProviders=true,DisableKubeletCloudCredentialProviders=true we can no longer schedule workloads due to taints and a lack of node configuration. This pulls a CCM image from K/cloud-provider-gcp to run tests. This is a pre-step for taking the above feature gates to beta. It does not address the last known good dependency issue. Specifically the CCM image is built on top of client-go and staging. However this image will be an "old" verison of those libraries. So it does not test if those libraries work in the CCM. Fix shellcheck errors. Add CCM_FEATURE_GATES for testing. Switching to extended regex from perl regex. Adding instrumentation to cluster configuration. Improved regex to not greedily get key-value pairs. Fixed issue with error on regex no line match. Switch credentialprovider version to v1alpha1 2022-10-21 17:36:05 -04:00			`apiVersion: rbac.authorization.k8s.io/v1`
			`kind: RoleBinding`
			`metadata:`
			`labels:`
			`addonmanager.kubernetes.io/mode: Reconcile`
			`name: system::leader-locking-cloud-controller-manager`
			`namespace: kube-system`
			`roleRef:`
			`apiGroup: rbac.authorization.k8s.io`
			`kind: Role`
			`name: system::leader-locking-cloud-controller-manager`
			`subjects:`
			`- kind: ServiceAccount`
			`name: cloud-controller-manager`
			`namespace: kube-system`
			`---`
			`apiVersion: rbac.authorization.k8s.io/v1`
			`kind: ClusterRoleBinding`
			`metadata:`
			`labels:`
			`addonmanager.kubernetes.io/mode: Reconcile`
			`name: system:cloud-controller-manager`
			`roleRef:`
			`apiGroup: rbac.authorization.k8s.io`
			`kind: ClusterRole`
			`name: system:cloud-controller-manager`
			`subjects:`
			`- kind: User`
			`apiGroup: rbac.authorization.k8s.io`
			`name: system:cloud-controller-manager`
			`---`
			`apiVersion: rbac.authorization.k8s.io/v1`
			`kind: ClusterRoleBinding`
			`metadata:`
			`labels:`
			`addonmanager.kubernetes.io/mode: Reconcile`
			`name: system:controller:cloud-node-controller`
			`roleRef:`
			`apiGroup: rbac.authorization.k8s.io`
			`kind: ClusterRole`
			`name: system:controller:cloud-node-controller`
			`subjects:`
			`- kind: ServiceAccount`
			`name: cloud-node-controller`
			`namespace: kube-system`