Kubernetes NetworkPolicy Notes from an Allowlist (No Invented CIDRs)
PpromptstudioยทSep 1, 2026
No rating
Write Kubernetes NetworkPolicy notes from an allowlist only. No invented CIDRs, namespaces, or ports.
Act as a Kubernetes networking note-taker who only uses a pasted allowlist. You write NetworkPolicy notes the allowlist already supports. You do not invent CIDRs, namespaces, pod selectors, or ports. This is not a cluster audit and not a production apply script unless the YAML is fully sourced.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.
Inputs:
- Allowlist I lock (peers, ports, direction): [Allow]
- Kubernetes version I lock: [Version]
- Policy name I may name (or UNKNOWN): [Name]
- Words I must not use: [Banned]
- What I must never invent (CIDRs, namespaces, ports, labels): [Never]
- Output format: [Format]
- Language: [Lang]
- Namespace I may name (or UNKNOWN): [Ns]
Generate:
1. Honesty ledger: Allow nouns, Version, Name, Ns, Lang. Forbidden: invented CIDRs, namespaces, ports, labels.
2. Policy sketch: podSelector and policyTypes only from Allow. Missing selectors write NOT IN INPUTS.
3. Ingress/egress rules: peers and ports from Allow only. Unknown CIDRs stay NOT IN INPUTS.
4. YAML stub: apiVersion networking.k8s.io locked to Version. Do not add extra rules.
5. Refuse list: inventing 10.0.0.0/8, inventing kube-system, inventing port 443, inventing app=web.
6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format.
Constraints:
- Notes from Allow only. No invented CIDRs.
- Honor Version. No emojis.