Kubernetes Interview Questions and Answers

A Pod is the smallest deployable unit in Kubernetes. It represents one or more containers that run together on the same node and share a network namespace, IP address, and storage volumes.

Key points:

• Containers in a Pod share localhost and can communicate over local ports.
• Pods are ephemeral. If a Pod dies, it is not restarted by itself; a controller such as a Deployment or StatefulSet recreates it.
• Common patterns include a main container plus sidecars for logging or proxying, init containers that run before the app, and ephemeral debug containers.
• Pods are usually managed indirectly rather than created directly.

kubectl get pods -o wide
kubectl describe pod web-6d4f9c-x2k
kubectl logs web-6d4f9c-x2k -c app

Because Pods share an IP, avoid binding two containers to the same port.

A namespace is a virtual cluster inside a physical cluster. It scopes names, RBAC, resource quotas, and network policies.

• Objects such as Pods, Services, and ConfigMaps are namespaced, while nodes and PersistentVolumes are cluster-scoped.
• Default namespaces include default, kube-system, and kube-public.
• Names provide DNS isolation: a Service in the dev namespace is dev.svc.cluster.local.
• ResourceQuota and LimitRange apply per namespace, which is useful for multi-tenant clusters.

kubectl create namespace staging
kubectl get pods -n staging
kubectl config set-context --current --namespace=staging

Namespaces are not a strong security boundary by themselves; combine RBAC, network policies, and separate clusters for hard isolation. Use namespaces to separate environments or teams operationally.