typhoon/addons/cluo/cluster-role-binding.yaml

apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: reboot-coordinator
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: reboot-coordinator
subjects:
  - kind: ServiceAccount
    namespace: reboot-coordinator
    name: default
addons: Switch to apps/v1 workload APIs * Deployments now belong to the apps/v1 API group * DaemonSets now belong to the apps/v1 API group * RBAC types now belong to the rbac.authorization.k8s.io/v1 API group 2018-02-10 23:51:55 -08:00			`apiVersion: rbac.authorization.k8s.io/v1`
Add Container Linux reboot-coordinator RBAC * Add a reboot-coordinator namespace for CLUO components * Define an RBAC ClusterRole for update-operator and update-agent * Replace the older-style where CLUO ran in kube-system, with admin privilege 2017-10-14 19:35:06 -07:00			`kind: ClusterRoleBinding`
			`metadata:`
			`name: reboot-coordinator`
			`roleRef:`
			`apiGroup: rbac.authorization.k8s.io`
			`kind: ClusterRole`
			`name: reboot-coordinator`
			`subjects:`
			`- kind: ServiceAccount`
			`namespace: reboot-coordinator`
			`name: default`