kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
  name: staging-user-role
rules:
- apiGroups: ["", "extensions", "apps", "batch", "autoscaling"]
  resources: ["deployments", "deployments/scale", "replicasets", "pods", "pods/log", "pods/exec", "pods/portforward",
              "nodes", "events", "configmaps", "persistentvolumes", "persistentvolumeclaims", "jobs", "cronjobs",
              "replicationcontrollers", "statefulsets", "ingresses", "services", "daemonsets", "namespaces", "horizontalpodautoscalers"]
  verbs: ["get", "list", "watch", "create", "update", "patch", "delete", "deletecollection"]

ksync doctor --context=staging
Extra Binaries                              ✓
Cluster Config                              ✓
Cluster Connection                          ✘
↳	Unable to contact the cluster for context (staging). Does 'kubectl --context=staging cluster-info' work?

kubectl --context=staging cluster-info
Kubernetes master is running at https://api.staging.domain.com
CoreDNS is running at https://api.staging.domain.com/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.

ksync doctor
Extra Binaries                              ✓
Cluster Config                              ✓
Cluster Connection                          ✓
Cluster Version                             ✓
Cluster Permissions                         ✓
Cluster Service                             ✓
Service Health                              ✓
Service Version                             ✓
Docker Version                              ✓
Docker Storage Driver                       ✓
Docker Storage Root                         ✓
Watch Running                               ✓
Everything looks good!                      ☺