The cluster was failing. Latency spiked, traffic bled across services, and nothing in the logs told the full story. You traced the issue to the service mesh, but the configs were tangled and stale. The fastest way forward was clear: git reset the service mesh and bring the system back to a known, stable state.
A service mesh adds powerful traffic control, security, and observability to microservices. But over time, configuration drift can break routing rules, disrupt mTLS, and complicate deployment pipelines. When the mesh settings stored in Git diverge from what’s deployed, debugging becomes guesswork. Resetting with Git re-aligns the mesh to the exact version you trust—no hidden overrides, no orphaned resources.
Git reset service mesh means returning mesh config files—YAML manifests, Helm charts, Istio or Linkerd settings—to a chosen commit. This removes partial changes pushed during failed experiments or rushed merges. It’s cleaner than patching broken configs one at a time because it ensures every component is rolled back together: ingress gateways, sidecars, policy sets, dashboards.