# Lovable — A Bug Hunt in Our Kubernetes Cluster

- Company: Lovable (lovable.dev)
- Announced: 2026-04-01T22:00:00+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://lovable.dev/blog/hunting-networking-bugs-in-kubernetes
- Record: https://forck.live/items/12092-a-bug-hunt-in-our-kubernetes-cluster
- Subject: Lovable / AI app builder

Lovable engineers debugged two layered networking failures in their Google Kubernetes Engine cluster. First, a concurrent map-access panic in Google's anetd WireGuard integration code caused pod crashes. After disabling transparent node-to-node encryption, a second issue emerged: an MTU mismatch between nodes that had and had not restarted, causing connection failures to Valkey. The fix required rolling all nodes to ensure consistent MTU configuration.

## Evidence

Verbatim from https://lovable.dev/blog/hunting-networking-bugs-in-kubernetes:

> When WireGuard was enabled, our cluster used an MTU (maximum transmission unit) of 1420 bytes to account for WireGuard's encryption overhead. Normally, Ethernet uses a standard MTU of 1500 bytes.

---

Record: https://forck.live/items/12092-a-bug-hunt-in-our-kubernetes-cluster
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md