<p>I am new in Kubernetes and I am trying to understand the concept of namespaces and context.<br />
It is basically allows to group resources into logical sets.<br />
An a context is the combination of user/cluster/namespace.<br />
What I am not sure is if namespaces provide any kind of isolation.<br />
E.g. if we have a user A that uses cluster C1 and namespace foo and user B that uses cluster C1 as well and the namespace foo, does any changes that user A does affect user B?<br />
E.g. if user A starts deleting pods would that be also visible by user B?</p>

Jim
<blockquote>
<p>What I am not sure is if namespaces provide any kind of isolation.
E.g. if we have a user A that uses cluster C1 and namespace foo and
user B that uses cluster C1</p>
</blockquote>
<p>Namespaces are for grouping resources. To control access to the C1 cluster by namespace, then it's doable via <a href="https://kubernetes.io/docs/reference/access-authn-authz/certificate-signing-requests/#normal-user" rel="nofollow noreferrer">creating <code>Roles</code>, and <code>RoleBindings</code> for the users and issuing certificates</a> that restrict access to a given namespace. It does not mean user A deployed pod cannot be accessed in runtime via a network call initiated from a pod deployed by user B in his bar namespace. For that network isolation, you need to use k8s <code>NetworkPolicies</code>.</p>
<blockquote>
<p>as well and the namespace foo, does any changes that user A does
affect user B? E.g. if user A starts deleting pods would that be also
visible by user B?</p>
</blockquote>
<p>Yes, it is visible. It's just the same cluster two users have access to the same namespace.</p>
