Need a deployment config for kubernetes with RBAC

Linkerd cannot retrieve endpoint list when deployed on kubernetes 1.6 using deployment configs as instructed https://linkerd.io/getting-started/k8s/ or https://linkerd.io/getting-started/k8s-daemonset/. This happends due to RBAC being turned on by default for kubernetes 1.6.

I circuvmented RBAC by permitting everything to default ServiceAccount used to run linkerd pod (see below).

We need a deployment config for kubernetes with RBAC with fine-grained Role (or ClusterRole? I am not an expert on Kubernetes).

If anyone needs the stack trace thown by linkerd, it is here #1344.

---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: RoleBinding
metadata:
  name: linkerd
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: linkerd-allow-all
subjects:
- kind: ServiceAccount
  name: default
  namespace: default
---
kind: Role
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
  name: linkerd-allow-all
rules:
  - apiGroups: [""]
    resources:
      - '*'
    verbs:
      - '*'

[esbie]

I believe this is resolved by https://buoyant.io/2017/07/24/using-linkerd-kubernetes-rbac/

[rmars]

@ethanrubio yeah I think you can do this without granting cluster-admin access. We’re working on adding example RBAC configs (see configs at https://github.com/linkerd/linkerd-examples/pull/165 for granting namerd access to the third party resource).