<p>My understanding is since pod is defined as a group of containers which provides shared resources such as storage and network among those containers, can it be thought of as a namespace in a worker node that is to say, different pods are representing different namespaces in a worker node machine?</p>

<p>Or otherwise is pod actually a process which is first started (or run or executed) by the deployment and then it starts the containers inside it? 
Can i see it through ps command? (I did try it, there are only docker containers running so I am ruling out pod being a process)</p>

emkay
<p>If we start from the basics</p>
<p><strong>What is a namespace (in a generic manner)?</strong></p>
<blockquote>
<p>A namespace is a declarative region that provides a scope to the identifiers (the names of types, functions, variables, etc) inside it. Namespaces are used to organize code into logical groups and to prevent name collisions that can occur especially when your code base includes multiple libraries.</p>
</blockquote>
<p><strong>What is a Pod (in K8s)?</strong></p>
<blockquote>
<p>A pod is a group of one or more containers (such as Docker containers), with shared storage/network, and a specification for how to run the containers. A pod’s contents are always co-located and co-scheduled, and run in a shared context. A pod models an application-specific “logical host” - it contains one or more application containers which are relatively tightly coupled — in a pre-container world, being executed on the same physical or virtual machine would mean being executed on the same logical host.</p>
<p>While Kubernetes supports more container runtimes than just Docker, Docker is the most commonly known runtime, and it helps to describe pods in Docker terms.</p>
<p>The shared context of a pod is a set of <strong>Linux namespaces</strong>, cgroups, and potentially other facets of isolation - the same things that isolate a Docker container. Within a pod’s context, the individual applications may have further sub-isolations applied.
<a href="https://kubernetes.io/docs/concepts/workloads/pods/pod/#what-is-a-pod" rel="noreferrer">Some deep dive into Pods</a></p>
</blockquote>
<p><strong>What is a Namespace (in k8s terms)?</strong></p>
<blockquote>
<p>Namespaces are intended for use in environments with many users spread across multiple teams, or projects.</p>
<p>Namespaces provide a scope for names. Names of resources need to be unique within a namespace, but not across namespaces.</p>
<p>Namespaces are a way to divide cluster resources between multiple users.</p>
</blockquote>
<p>So I think its suffice to say:</p>
<p><strong>Yes Pods have a namespace</strong> :</p>
<blockquote>
<p>Pods kind of represent a namespace but on a container level (where they share the same context of networks, volumes/storage only among a set of containers)</p>
<p>But namespaces (in terms of K8s) are a bigger level of isolation -- on a cluster level which shared by all the containers (services, deployments, dns-names, IPs, config-maps, secrets, roles, etc).</p>
</blockquote>
<p>Also you should see this <a href="https://stackoverflow.com/q/33472741/5833562">link</a></p>
<p>Hope this clears a bit of fog on the issue.</p>
