cilium

What problem does it solve?

This Skill helps you operate and troubleshoot Cilium on K3s when cluster networking, load balancer IP assignment, or ingress behavior becomes difficult to diagnose. It turns low-level Cilium state into clear next steps for an ARM64 homelab cluster.

Core Features & Use Cases

• kube-proxy replacement checks: Validate that Cilium is correctly handling service routing, BPF behavior, and masquerading.
• Gateway API and ingress troubleshooting: Confirm Envoy CRDs, GatewayClass status, and shared or dedicated ingress exposure.
• Load balancer and LAN advertising: Inspect LB-IPAM pools, external IP assignment, and L2 announcements for DNS and HTTP VIPs.
• Upgrade and failure recovery: Detect stale operator pods, pending Helm upgrades, and rollout issues after configuration changes.
• Use case: When a GatewayClass stays Unknown or a LoadBalancer service never gets an IP, use this Skill to identify the missing pool, stale pod, or traffic-policy mismatch.

Quick Start

Ask the assistant to inspect the current Cilium deployment, report networking health, and recommend the next fix for any kube-proxy, Gateway API, LB-IPAM, or L2 announcement issue.