One OKE cluster hosts both the clerk portal and the inspector mobile API for a city. What orchestration constructs slice the cluster so a Service or controller affects only the intended replica set?
Select an answer to reveal the explanation.
Short Explanation
Namespaces are neighborhoods; labels are name tags on each house. Controllers and Services use those tags to touch this set of replicas, not every container on the node. That is cluster slicing, not a tenancy redesign.
Full Explanation
Kubernetes namespaces provide scoping for teams and releases; labels and selectors identify which Pods a Deployment, Service, or policy applies to. That isolation model is inside the orchestrator. Compartment redesign is an OCI tenancy concern and is out of scope here. Name-only binding and selector-less exposure break the intended selection model.