Menu

When the mesh fights Kubernetes: a webhook deadlock, a probe loop, and what it costs
📰

When the mesh fights Kubernetes: a webhook deadlock, a probe loop, and what it costs

DEV Community: go·Anthony Amoah·9 days ago
#t2OxHKek
#devtogo#devto#dev#sidecar#webhook
Reading 0:00
15s threshold

In part 1 , we rigged the network so every packet in the pod passes through Ananse's sidecar, without the app knowing. That was the plan on paper. This post is about what happened when the plan met a real cluster.

Two bugs taught me the most. In the first, the mesh locked its own control plane out of the cluster. In the second, a routine health check made the sidecar call itself until it drowned in timeouts. After that, I'll cover what running the mesh actually costs, and what I'd change next.

The Deadlock (The Webhook Injecting Into Its Own Namespace)

In Ananse Service Mesh, the control plane runs a Mutating Admission Webhook. Crucially, this webhook is configured with failurePolicy: Fail . This is a deliberate security choice: if the webhook cannot be reached, pod creation is rejected. If we used Ignore , pods would silently start without a sidecar, breaking mTLS and routing without anyone noticing.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.