<p>I'm a little confused about the default Service Account in new created Namespace in my Minikube.</p>
<ul>
<li>Does it have any permissions? It seems not because I can't find any rolebinding or clusterrolebindung which references this SA</li>
<li>Then why is it created when it does not have a permission, or is there a use case around that?</li>
<li>and lastly, why are service accounts by default mount to pods?</li>
</ul>
<p>Regards
ralph</p>

ralph
<ol>
<li><p>The default <a href="https://thenewstack.io/kubernetes-access-control-exploring-service-accounts/" rel="nofollow noreferrer">service account</a> doesn’t have enough permissions to retrieve the services running in the same namespace.</p>
</li>
<li><p>Kubernetes follows the convention of closed-to-open which means that by default no user or service account has any permissions.</p>
<p>To fulfill this request, we need to create a role binding associating the default service account with an appropriate role.This is similar to how we assign a viewer role to the service account that can give permission to list pods.</p>
</li>
<li><p>Pods have the default service account assigned even when you don’t ask for it. This is because every pod in the cluster needs to have one (and only one) service account assigned to it.</p>
<p>Refer <a href="https://stackoverflow.com/questions/52995962/kubernetes-namespace-default-service-account">Kubernetes namespace default service account</a> for more information.</p>
</li>
</ol>
