Kubernetes Load Balancing and Hedgedoc

The problem

Internal services needed predictable load balancing inside Kubernetes, and teams were losing context in email threads that should have been shared, editable documents.

What I implemented

I deployed HAProxy-based load balancers for internal Kubernetes traffic patterns that needed more control than a default Service type could offer. In parallel, I rolled out Hedgedoc — self-hosted markdown collaboration — to replace fragmented email workflows with something searchable and version-friendly.

Why both belong in the same story

One is pure infrastructure plumbing; the other is developer experience. Both reduce friction. Reliable load balancing keeps services reachable; shared docs keep decisions and runbooks where everyone can find them.

What I took away

Platform work spans the stack — from packets to people. The best internal tools are the ones that disappear into the workflow until someone tries to live without them.