From a civic Kubernetes worker-node foothold, the tester notices pod networks that look flatter than the surrounding datacenter VLANs. What awareness should guide further pivoting?
Select an answer to reveal the explanation.
Short Explanation
Landing on a K8s node is not the same as standing in a normal VLAN closet. Pod overlays and namespaces can change what you can see and reach. Map carefully inside scope before you assume the old segmentation story still holds.
Full Explanation
Kubernetes networking often uses overlays, CNI plugins, and namespaces that differ from classic datacenter VLAN boundaries. A foothold on a worker node may observe pod ranges or paths that look flatter or differently segmented than adjacent infrastructure. Testers should enumerate that visibility carefully and stay within written scope rather than assuming either total isolation or blanket authorization. Control-plane exploitation is a separate, RoE-bound decision—not implied by flat-looking pod networks.