<p>We are using a K8s cluster but we don't have cluster level permissions, so we can only create <code>Role</code> and <code>ServiceAccount</code> on our namespaces and we need install a service mesh solution (Istio or Linkerd) only in our namespaces.</p>

<p>Our operation team will agree to apply CRDs on the cluster for us, so that part is taken care of, but we can’t request for cluster admin permissions to set up the service mesh solutions.</p>

<p>We think that it should be possible to do this if we change all the <code>ClusterRole</code>s and <code>ClusterRoleBinding</code>s to <code>Role</code>s and <code>RoleBinding</code>s on Helm charts.</p>

<p>So, the question is: how can we set up a service mesh using Istio or Linkerd without having admin permission on the K8s cluster?</p>

Ali Rajabi
<p>Linkerd cannot function without certain ClusterRoles, ClusterRoleBindings, etc. However, it does provide a two-stage install mode where one phase corresponds to "cluster admin permissions needed" (aka give this to your ops team) and the other "cluster admin permissions NOT needed" (do this part yourself).</p>

<p>The set of cluster admin permissions needed is scoped down to be as small as possible, and can be inspected (The <code>linkerd install config</code> command simply outputs it to stdout.)</p>

<p>See <a href="https://linkerd.io/2/tasks/install/#multi-stage-install" rel="nofollow noreferrer">https://linkerd.io/2/tasks/install/#multi-stage-install</a> for details.</p>

<p>For context, we originally tried to have a mode that required no cluster-level privileges, but it became clear we were going against the grain with how K8s operates, and we ended up abandoning that approach in favor of making the control plane cluster-wide but multi-tenant.</p>
