{
  "id": 1956453,
  "title": "I Replaced kube-proxy with eBPF in Production (And Why My Monitoring Went Blind for 6 Hours)",
  "url": "https://urgent.news/2026/08/19/i-replaced-kube-proxy-with-ebpf-in-production-and-why-my-monitoring",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-08-19T15:00:32.000Z",
  "source": {
    "name": "Dev.to",
    "slug": "dev-to",
    "url": "https://dev.to/le_beltagy/i-replaced-kube-proxy-with-ebpf-in-production-and-why-my-monitoring-went-blind-for-6-hours-1lkb"
  },
  "original_language": "en",
  "account": "In a production environment, a system administrator replaced the kube-proxy component with eBPF in Cilium. The upgrade occurred on a Tuesday evening, and initially, everything seemed to function as expected. However, at 2:47 AM, an unusual alert was received by the monitoring system - the SIEM. The absence of data from the SIEM led to a 6-hour outage, with the security information and event management system unable to detect any packets. This incident highlighted the importance of monitoring the one metric that mattered: the connection tracking visibility provided by the iptables rules in kube-proxy.",
  "summary": "I Replaced kube-proxy with eBPF in Production (And Why My Monitoring Went Blind for 6 Hours) From a \"simple\" Cilium upgrade to a 6-hour outage where my SIEM couldn't see a single packet — the real story of deleting kube-proxy, the invisible eBPF datapath, and why the docs never warned me about the one metric that matters. The Setup It started with a cilium upgrade command I ran on a Tuesday…",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}