cilium-expert

Generate Cilium eBPF networking configurations for Kubernetes with least-privilege policies.

3|1|Updated Dec 3, 2025
One-click install
npx skills add https://github.com/Probably-Group/Dev-AID --skill cilium-expert-probably-group
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cilium-expert
Source: https://github.com/Probably-Group/Dev-AID/tree/main/.dev-aid/skills/expert/cilium-expert
Command: npx skills add https://github.com/Probably-Group/Dev-AID --skill cilium-expert-probably-group

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about cilium-expert

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

FAQPage Schema
How do I create a default-deny Kubernetes network policy with Cilium?

To create a default-deny Kubernetes network policy with Cilium, you define a CiliumNetworkPolicy that blocks all ingress and egress traffic, then adds explicit allow rules for approved communication. This enforces least-privilege access instead of relying on permissive defaults.

How does Cilium enforce L7 HTTP authorization for zero trust access?

Cilium enforces L7 HTTP authorization for zero trust access by applying CiliumNetworkPolicy rules that restrict specific HTTP methods, paths, and headers. This allows fine-grained API gateway protection beyond basic L3/L4 network connectivity controls.

Can I restrict Kubernetes workload egress traffic to specific external domains?

You can restrict Kubernetes workload egress traffic to specific external domains by using Cilium egress FQDN control. This leverages DNS-based policies within CiliumNetworkPolicy resources to limit outbound connections to approved fully qualified domain names.

What's the best way to set up Hubble observability for Kubernetes network policy auditing?

The best way to set up Hubble observability for Kubernetes network policy auditing is to configure it alongside Cilium. This provides audit-ready troubleshooting and visibility into traffic flows, verifying that your identity-based network policies are enforced correctly.

Does Cilium network policy rely on IP addresses for pod selection?

Cilium network policy does not rely on IP addresses for pod selection. It uses identity-based selection within CiliumNetworkPolicy resources, avoiding IP assumptions to maintain secure and stable Kubernetes workload communication rules.

Are there version compatibility constraints when enabling Cilium encryption in Kubernetes?

Yes, there are version compatibility constraints when enabling Cilium encryption in Kubernetes. You must meet minimum compatible Cilium, Hubble, and Kubernetes versions to successfully enable WireGuard or IPsec encryption and verify its operation.