Namespaces organize many resources and support scoped policy. They do not automatically provide complete network or security isolation.
Before you start
You should understand Pods, Deployments and Services. Read desired configuration separately from observed cluster state. Use a development cluster when trying changes, and inspect events and status rather than assuming that an accepted manifest means the workload is ready to serve traffic.
The practical goal is to reason through this situation: Separate teams can receive namespace-scoped permissions and quotas. Read the walkthrough first, then try the interview exercise before opening its answer. The important part is explaining the decision and its consequences, rather than remembering a definition alone.
Step-by-step walkthrough
Step 1: Define organizational scope
Namespaces group resources and support scoped policy.
Step 2: Add isolation controls
RBAC, network policy and quotas address different boundaries.
Step 3: Evaluate shared infrastructure
Shared nodes may not satisfy every tenant threat model.
Worked scenario
Separate teams can receive namespace-scoped permissions and quotas.
Team A and B run in different namespaces but may still reach each other’s services if network policy does not prohibit it. Namespace-scoped permissions can prevent API access while leaving network access unchanged. Resource quotas constrain consumption but do not substitute for either permission or traffic controls.
Common mistake
Putting workloads in different namespaces does not inherently block communication.
Verify the behavior
Test API permissions, cross-namespace traffic and resource limits independently.
Interview exercise
Build a stronger tenant boundary.
Answer and reasoning
Combine appropriate authorization, network policy and resource controls, and evaluate whether shared nodes meet the threat model.
Continue learning
Compare the scenario with the Kubernetes interview questions and test your understanding with the Kubernetes MCQs. For terminology and implementation details, consult the reference material.