Kubetier
← Permission Reference
T2

create networkpolicies

NetworkPolicy allow rules are additive across every policy selecting a pod for a given direction.

A new permissive policy reopens access without touching existing restrictive ones, and leaves less of an audit trail than a patch or delete.

API Group
networking.k8s.io
Scope
namespaced
Audit Level
RequestResponse

Escalation Paths

  1. Create a second NetworkPolicy selecting the same pods, with an unconditional allow rule for ingress or egress.

  2. Allowed traffic is the union of every policy that selects the pod, so the permissive rule reopens what the restrictive policy closed.

  3. The restrictive policy is untouched and still present, so an audit or GitOps diff of existing objects shows it intact.

  4. Patching an existing policy reaches the same result by adding allow rules or by narrowing its podSelector so it stops selecting the target.

  5. Quieter than deletion, because nothing that was there is missing.

    The new object is the only evidence.

Additional rights needed:

none
K8s docs ↗
K8s docs ↗