What problem does it solve?
It helps you design and generate correct, secure Cilium networking configurations so your Kubernetes workloads communicate with least-privilege access rather than relying on permissive defaults.
Core Features & Use Cases
- CiliumNetworkPolicy security-by-default: Produces default-deny style policies (no “allow all”) with explicit ingress/egress allowances.
- L7-aware enforcement: Applies HTTP method/path/header constraints for zero-trust access control and API gateway protection.
- Encryption, egress control, and observability: Guides enabling WireGuard/IPsec-style encryption, restricting external egress via FQDN+DNS, and configuring Hubble for audit-ready troubleshooting.
- Version-safe guardrails: Enforces minimum compatible Cilium/Hubble/kubernetes versions and highlights common policy-security pitfalls.
Quick Start
Use the cilium-expert skill to generate a CiliumNetworkPolicy that implements a default-deny stance and then allows only frontend-to-backend TCP/8080 traffic with strict HTTP path and method rules.