<p>I've got an issue, I'm trying to install linkerd on my cluster, all is going well</p>
<p>I went exactly with this official README</p>
<pre class="lang-sh prettyprint-override"><code>https://linkerd.io/2.11/tasks/install-helm/
</code></pre>
<p>installed it via helm</p>
<pre class="lang-sh prettyprint-override"><code>MacBook-Pro-6% helm list -n default
NAME        NAMESPACE   REVISION    UPDATED                                 STATUS      CHART           APP VERSION
linkerd2    default     1           2021-12-15 15:47:10.823551 +0100 CET    deployed    linkerd2-2.11.1 stable-2.11.1
</code></pre>
<p>linkerd itself works, and the <code>linkerd check</code> command as well</p>
<pre class="lang-sh prettyprint-override"><code>MacBook-Pro-6% linkerd version
Client version: stable-2.11.1
Server version: stable-2.11.1
</code></pre>
<p>but when I try to install <code>viz</code> dashboard as described in the <a href="https://linkerd.io/2.11/getting-started/" rel="nofollow noreferrer">getting-started</a> page I run</p>
<pre class="lang-sh prettyprint-override"><code>linkerd viz install | kubectl apply -f -
</code></pre>
<p>and when going with</p>
<pre class="lang-sh prettyprint-override"><code>linkerd check
...
Status check results are √

Linkerd extensions checks
=========================
/ Running viz extension check
</code></pre>
<p>and it keeps on checking the viz extensions, and when I ran <code>linkerd dashboard</code> (deprecated I know) shows the same error</p>
<pre class="lang-sh prettyprint-override"><code>Waiting for linkerd-viz extension to become available
</code></pre>
<p>anyone got any clue what I'm doing wrong ? Been stuck at this part for 2hrs &amp;_&amp; and noone seem to have any answers</p>
<p>note, when I ran, <code>linkerd check</code> after instalation of viz I get</p>
<pre class="lang-sh prettyprint-override"><code>
linkerd-viz
-----------
√ linkerd-viz Namespace exists
√ linkerd-viz ClusterRoles exist
√ linkerd-viz ClusterRoleBindings exist
√ tap API server has valid cert
√ tap API server cert is valid for at least 60 days
‼ tap API service is running
    FailedDiscoveryCheck: failing or missing response from https://10.190.101.142:8089/apis/tap.linkerd.io/v1alpha1: Get &quot;https://10.190.101.142:8089/apis/tap.linkerd.io/v1alpha1&quot;: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
    see https://linkerd.io/2.11/checks/#l5d-tap-api for hints
‼ linkerd-viz pods are injected
    could not find proxy container for grafana-8d54d5f6d-cv7q5 pod
    see https://linkerd.io/2.11/checks/#l5d-viz-pods-injection for hints
√ viz extension pods are running
× viz extension proxies are healthy
    No &quot;linkerd-proxy&quot; containers found in the &quot;linkerd&quot; namespace
    see https://linkerd.io/2.11/checks/#l5d-viz-proxy-healthy for hints
</code></pre>
<hr />
<p>debugging</p>

<p>From your problem descripiton:</p>
<blockquote>
<p>‼ linkerd-viz pods are injected
could not find proxy container for grafana-8d54d5f6d-cv7q5 pod
see <a href="https://linkerd.io/2.11/checks/#l5d-viz-pods-injection" rel="nofollow noreferrer">https://linkerd.io/2.11/checks/#l5d-viz-pods-injection</a> for hints</p>
</blockquote>
<p>and:</p>
<blockquote>
<p>MacBook-Pro-6% helm list -n default</p>
</blockquote>
<p>I encountered a similar problem but with <code>flagger</code> pod rather than <code>grafana</code> pod (I didn't attempt to install <code>grafana</code> component like you did).</p>
<p>A side effect of my problem is this:</p>
<pre><code>$ linkerd viz dashboard
Waiting for linkerd-viz extension to become available
Waiting for linkerd-viz extension to become available
Waiting for linkerd-viz extension to become available
... ## repeating for 5 minutes or so before popping up the dashboard in browser.
</code></pre>
<p>The cause for my problem turned out to be that I installed the <code>viz</code> extension into the <code>linkerd</code> namespace. It should belong to the <code>linkerd-viz</code> namespace.</p>
<p>Looking at your original problem description, it seems that you installed the control plane into the <code>default</code> namespace (as opposed to the <code>linkerd</code> namespace.) While you can use any namespace you want, the control plane must be in a separate namespace from the <code>viz</code> extension. Details can be seen in the discussion I wrote here:</p>
<ul>
<li><a href="https://github.com/linkerd/website/issues/1309" rel="nofollow noreferrer">https://github.com/linkerd/website/issues/1309</a></li>
</ul>
