You want to allow a pod in namespace frontend to access a service backend in namespace api. Which steps are needed to enable this cross-namespace communication?
hard📝 Best Practice Q15 of 15
Kubernetes - Namespaces
You want to allow a pod in namespace frontend to access a service backend in namespace api. Which steps are needed to enable this cross-namespace communication?
AUse the full DNS name <code>backend.api.svc.cluster.local</code> and configure network policies to allow traffic from <code>frontend</code> to <code>api</code>
BCreate a service account in <code>frontend</code> and bind it to <code>api</code> namespace
CExpose the backend service as NodePort and access it via node IP
DDeploy the backend service in <code>frontend</code> namespace instead
Step-by-Step Solution
Solution:
Step 1: Use correct DNS name for cross-namespace access
Accessing a service in another namespace requires the full DNS name: backend.api.svc.cluster.local.
Step 2: Configure network policies
Network policies must allow traffic from pods in frontend namespace to api namespace services.
Final Answer:
Use the full DNS name backend.api.svc.cluster.local and configure network policies to allow traffic from frontend to api -> Option A
Quick Check:
DNS + network policy = cross-namespace communication [OK]
