coredns/dynapi v0.1.0: an HTTP API for CoreDNS records, 8 years later

tl;dr coredns/dynapi v0.1.0 is out, published on 2026-10-01. It is an external CoreDNS plugin. Applications read, replace and delete A and AAAA record sets through a JSON HTTP API. The idea started as coredns/coredns#1822. I opened that PR on 2018-05-20. It was closed on 2018-09-29, when the coredns/dynapi repository was created. That repository stayed empty for eight years. The plugin in v0.1.0 is a new design, not a port of the old code. Why I needed it At SumUp we had what felt like an amazing idea: build our own take on ArgoCD. It was a Kubernetes-based deployment system for on-demand dev environments, and it ran on bare metal instances. It worked. ...

October 2, 2026 · 10 min

OneTUI 0.2.0: writes, CQL and one way to query everything

OneTUI 0.2.0 adds provider-specific write operations, ScyllaDB and Cassandra support, and a multi-line query editor. It keeps the same resource browser and query workflow across seven data sources. This post follows the 0.1.0 release story. What’s new Provider-specific write operations in the shared editor. Each provider uses its own query or command syntax; OneTUI does not translate every source into one universal language. ScyllaDB and Cassandra through one CQL provider. Per-language syntax highlighting, multi-line editing, and query history. Confirmation before a command runs, enabled by default with ask_for_query_confirm. Connection errors shown in a popup. Optional literal username and password fields in connection configuration. Keep files with literal credentials private. The seven providers are PostgreSQL, Kafka, NATS, DynamoDB, RabbitMQ, Qdrant, and CQL for ScyllaDB or Cassandra. “Write” means the operation each provider exposes, such as a SQL statement, a published message, or an HTTP request. ...

September 28, 2026 · 6 min

OneTUI: one terminal, every data source

tl;dr Code is at github.com/syndbg/onetui. If the idea of one consistent TUI across your databases and queues sounds useful to you too, I’d like to hear about it. Over the years I’ve used DBeaver, DataGrip, psql, and whatever Kafka CLI happened to be the flavor of the month. Each one does its job, more or less. None of them feel like the same tool. Keybinds differ. Panels differ. Some support the data source I need that day, some don’t. Some barely work. ...

September 20, 2026 · 8 min

On writing small useful things like zjyo

I’ve used z for over a decade. Not zoxide, not jump, not fasd, the original rupa/z, a few hundred lines of POSIX shell that tracks the directories you cd into and lets you jump back with a fuzzy pattern instead of a full path. At some point I tried the newer alternatives. Each one changed something I didn’t ask it to change: a different ranking algorithm, a different database format, a new set of flags to relearn. None of them were bad tools. They just weren’t z. I wanted the exact behavior I already had muscle memory for, just without a shell interpreter parsing a database file on every invocation. ...

September 19, 2026 · 5 min

Writing a Kubernetes Cloud Controller Manager: Bridging Your Infra to Kubernetes

A Cloud Controller Manager (CCM) connects Kubernetes to cloud or private-infrastructure APIs. Its controllers add provider-specific node data and manage services or routes the cluster cannot create itself. Without a cloud provider that supports them, Kubernetes cannot populate some cloud-specific node fields or provision a cloud load balancer for type: LoadBalancer. I’ve spent a good chunk of time in this code, both building on top of kubernetes/cloud-provider directly and reading through what Hetzner’s and DigitalOcean’s CCMs do differently. This post covers the interface, the four control loops that drive it, the full node/route/service lifecycle, and the patterns worth stealing once you’ve got the basics working. ...

August 6, 2026 · 26 min

Git Worktrees: Parallel Development Without Cloning Everything Twice

I knew about Git worktrees for years before I used them regularly. I reached for them when switching branches started costing more than opening another directory: a server was running, generated files had changed, or a review arrived in the middle of unfinished work. A worktree gives a branch its own working directory while reusing the repository’s Git object database. You still get a separate checkout and separate build artifacts. You avoid cloning the full Git history again or stashing work just to inspect another branch. The same setup also gives a coding agent an isolated directory to change. ...

May 2, 2026 · 12 min

Building a Kubernetes CSI Driver: Services, Sidecars, and Volume Flow

Kubernetes does not call a storage vendor directly when a pod mounts a volume. The Container Storage Interface (CSI) defines the gRPC boundary between Kubernetes and the driver that talks to the storage system. I contributed to a production CSI driver and wrote this guide to explain the services, sidecars, and volume calls that are easiest to mix up. The code blocks show focused patterns. They are not a complete, copy-and-run driver. ...

April 24, 2026 · 15 min

How Go 1.25 Changes GOMAXPROCS in Containers

A Go container can be limited to one CPU while the runtime sees all 32 logical CPUs on its node. Before Go 1.25, the runtime could schedule work as if all 32 were available. When a burst of CPU-bound work used the container’s quota, Linux could pause the whole container until its quota renewed. Requests that were ready to run then waited, which can show up as latency spikes under load. ...

January 13, 2025 · 5 min