bc-gov-networkpolicy

Author and validate Kubernetes NetworkPolicy manifests for OpenShift clusters.

7|Updated Mar 5, 2026

Search Tags:#kubernetes #openshift #ingress #network-security #networkpolicy #egress #bc-gov

Ready to run

npx skills add https://github.com/rloisell/rl-agents-n-skills --skill bc-gov-networkpolicy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: bc-gov-networkpolicy
Source: https://github.com/rloisell/rl-agents-n-skills/tree/main/bc-gov-networkpolicy
Command: npx skills add https://github.com/rloisell/rl-agents-n-skills --skill bc-gov-networkpolicy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents silent network failures and insecure egress by providing clear, repeatable patterns and checks for Kubernetes/OpenShift NetworkPolicy authoring across BC Gov private cloud environments.

Core Features & Use Cases

Two-policy rule guidance ensuring every traffic flow has both sender Egress and receiver Ingress policies.
Mandatory DNS egress reminder and patterns for same-namespace flows, inter-namespace selectors, and CIDR-based external egress.
ag-helm intent API recommendations and Conftest-compatible constraints for Emerald guardrails, plus a troubleshooting checklist and useful oc commands for diagnosis.

Quick Start

Generate or validate a NetworkPolicy that provides DNS egress and implements the two-policy rule for frontend to api communication in the target namespace.

Frequently Asked Questions about bc-gov-networkpolicy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I write a Kubernetes NetworkPolicy for BC Gov OpenShift clusters?▼

To write a Kubernetes NetworkPolicy for BC Gov OpenShift, you must enforce least-privilege network flows by applying the two-policy rule, ensuring both sender egress and receiver ingress policies are created for every traffic flow across Silver, Gold, or Emerald environments.

Why does my inter-namespace communication fail after applying a NetworkPolicy?▼

Inter-namespace communication fails when NetworkPolicy rules are incomplete. You need the two-policy rule to create matching sender egress and receiver ingress policies, plus mandatory DNS egress allowances on port 53 for namespace resolution to succeed.

Do I need to allow DNS egress for same-namespace NetworkPolicy flows?▼

Yes, you must allow DNS egress for same-namespace NetworkPolicy flows. Mandatory DNS egress reminders ensure applications can resolve internal services, requiring explicit port-specific selectors to prevent silent network failures in BC Gov private cloud environments.

Can I use ag-helm intent API compatibility with OpenShift NetworkPolicy?▼

Yes, you can use ag-helm intent API compatibility with OpenShift NetworkPolicy. The Skill provides specific recommendations for ag-helm intent APIs and ensures conformance to ag-devops Conftest gate constraints required for Emerald environment guardrails.

What is the best way to debug silent network failures in BC Gov private cloud?▼

The best way to debug silent network failures is using the provided troubleshooting checklist and oc commands to diagnose NetworkPolicy issues. This validates two-policy sender and receiver rules, DNS port allowances, and CIDR-based external egress configurations.

Does this NetworkPolicy approach support CIDR-based external egress?▼

Yes, this NetworkPolicy approach supports CIDR-based external egress. It provides clear, repeatable patterns for configuring external traffic flows alongside inter-namespace selectors, ensuring secure egress conformance within BC Gov OpenShift clusters.