NyxClusterNetworkPolicy is the cluster-scoped policy resource. Unlike NyxNetworkPolicy, it isn’t bound to a single namespace — it selects namespaces with a namespaceSelector and applies across the cluster. It’s the resource platform teams use for cluster-wide overrides and baselines.
Example
A platform-override that denies all public-internet egress from production namespaces. The low priority (50) puts it in the platform-override band, so it wins over any namespace or workload policy:
Spec
string
required
Must be
platform. Marks the policy as platform-managed.integer
default:"100"
Evaluation priority, 0–99,999. Lower numbers are evaluated first and win. Must fall within a band the admission webhook permits; see Priority System. Defaults to
100.string
default:"enforce"
Enforcement mode for this policy’s
Deny rules: dry-run, audit, or enforce. See Enforcement Modes. Defaults to enforce.object
Selects the namespaces this policy applies to, using the label selector shape. Omit it (or leave it empty) to apply to all namespaces.
object
Narrows the policy to specific pods within the matched namespaces, using the label selector shape. Omit it to apply to all pods.
array of string
Which directions this policy governs:
Ingress, Egress, or both.array
Ingress rules, evaluated top-down. The first matching rule decides the verdict.
array
Egress rules, evaluated top-down. The first matching rule decides the verdict.
NyxNetworkPolicy.
Status
Nyx populatesstatus on each policy — it’s read-only. Fields include phase (Pending, Active, or Failed), appliedAt, affectedPods (name, namespace, nodeName, ip), nodesApplied, and a human-readable message.