<p>The Kubernetes Dashboard allows users to see all secrets, including their raw values with just a couple clicks. These secrets will likely contain very sensitive data, such as production database passwords and private keys.</p>

<p>How do you limit users of the Dashboard, so that they can't see the sensitive data?</p>

<p>This is a <a href="https://github.com/kubernetes/dashboard/issues/964" rel="nofollow noreferrer">known issue</a> and it is simply not officially supported at the moment - the Dashboard is a super-user level administration tool. This <a href="https://github.com/kubernetes/dashboard/issues/964#issuecomment-292486020" rel="nofollow noreferrer">should not be the case</a> forever, but more help is needed to get it there.</p>

<p>There are some workarounds discussed in that issue thread that work currently. Here are some notable quirks around them to be aware of beforehand:</p>

<ul>
<li>Should the dashboard be under a dashboard user, and limited by that? If so, like Anirudh suggested you can neuter parts of the Dashboard and it will work fine and get 403s if they access the Secrets panel.</li>
<li>Should the dashboard be under a logged in user, and be limited to what that user can see? This means that <code>kubectl proxy</code> will be necessary without some browser plugin or MITM proxy to attach the needed auth to dashboard server calls but it <a href="https://github.com/kubernetes/dashboard/issues/964#issuecomment-240496867" rel="nofollow noreferrer">is possible</a>.</li>
</ul>
