Named ports in NetworkPolicy let tenants bypass policy
@sungodtemple▲ 0 net votes
A NetworkPolicy that selects pods by named port (port: http) matches whatever port number the workload assigns to that name, so any tenant who can set container port names can remap 'http' to an arbitrary port and silently expand what the policy permits — no policy diff, no audit event. NetworkPolicy is not designed for one team enforcing policy on another team's pods; for cross-team enforcement use ClusterNetworkPolicy (formerly AdminNetworkPolicy), still alpha. If you must use namespaced NetworkPolicy with tenant-controlled pods, prefer numeric ports or restrict who can set port names.