instruction: Create a Kubernetes configuration with Group, ClusterRoleBinding, ClusterRole resources
output: ```dockerfile
  from v1.18 cannot join a cluster created by kubeadm v1.17.
  To workaround the issue you have two options:
  Execute kubeadm init phase bootstrap-token on a control-plane node using kubeadm v1.18.
  Note that this enables the rest of the bootstrap-token permissions as well.
  or
  Apply the following RBAC manually using kubectl apply -f ...:
  apiVersion: rbac.authorization.k8s.io/v1
  kind: ClusterRole
  metadata:
   name: kubeadm:get-nodes
  rules:
   - apiGroups:
   - ""
   resources:
   - nodes
   verbs:
   - get
  ---
  apiVersion: rbac.authorization.k8s.io/v1
  kind: ClusterRoleBinding
  metadata:
   name: kubeadm:get-nodes
  roleRef:
   apiGroup: rbac.authorization.k8s.io
   kind: ClusterRole
   name: kubeadm:get-nodes
  subjects:
   - apiGroup: rbac.authorization.k8s.io
   kind: Group
   name: system:bootstrappers:kubeadm:default-node-token
  ebtables or some similar executable not found during installation
  If you see the following warnings while running kubeadm init
  [preflight] WARNING: ebtables not found in system path
  [preflight] WARNING: ethtool not found in system path
  Then you may be missing ebtables, ethtool or a similar executable on your node.
  You can install them with the following commands:
  
  For Ubuntu/Debian users, run apt install ebtables ethtool.
  For CentOS/Fedora users, run yum install ebtables ethtool.
  
  kubeadm blocks waiting for control plane during installation
  If you notice that kubeadm init hangs after printing out the following line:
  [apiclient] Created API client, waiting for the control plane to become ready
  This may be caused by a number of problems. The most common are:
  
  network connection problems. Check that your machine has full network connectivity before continuing.
  the cgroup driver of the container runtime differs
  ```