kubespray/roles/dnsmasq/templates/dnsmasq-clusterrolebinding....

---
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
  name: dnsmasq
  namespace: "kube-system"
subjects:
  - kind: ServiceAccount
    name: dnsmasq
    namespace: "kube-system"
roleRef:
  kind: ClusterRole
  name: cluster-admin
  apiGroup: rbac.authorization.k8s.io
Apply ClusterRoleBinding to dnsmaq when rbac_enabled (#1592) * Add RBAC policies to dnsmasq * fix merge conflict * yamllint * use .j2 extension for dnsmasq autoscaler 2017-09-03 15:53:45 +08:00			`---`
			`kind: ClusterRoleBinding`
			`apiVersion: rbac.authorization.k8s.io/v1beta1`
			`metadata:`
			`name: dnsmasq`
Stop templating kube-system namespace and creating it (#2545) Kubernetes makes this namespace automatically, so there is no need for kubespray to manage it. 2018-03-30 19:29:13 +08:00			`namespace: "kube-system"`
Apply ClusterRoleBinding to dnsmaq when rbac_enabled (#1592) * Add RBAC policies to dnsmasq * fix merge conflict * yamllint * use .j2 extension for dnsmasq autoscaler 2017-09-03 15:53:45 +08:00			`subjects:`
			`- kind: ServiceAccount`
			`name: dnsmasq`
Stop templating kube-system namespace and creating it (#2545) Kubernetes makes this namespace automatically, so there is no need for kubespray to manage it. 2018-03-30 19:29:13 +08:00			`namespace: "kube-system"`
Apply ClusterRoleBinding to dnsmaq when rbac_enabled (#1592) * Add RBAC policies to dnsmasq * fix merge conflict * yamllint * use .j2 extension for dnsmasq autoscaler 2017-09-03 15:53:45 +08:00			`roleRef:`
			`kind: ClusterRole`
			`name: cluster-admin`
			`apiGroup: rbac.authorization.k8s.io`