Architecture

The etcd cluster is up and waiting for data. Here’s why copying everything over as-is didn’t work out — and how the migration turned into a full rethink of the data schemas.

First component: the management cluster on Kubernetes.

The concept behind Architecture 2.0.

Architecture 2.0 is taking shape — time to build. First component: a Kubernetes management cluster. But before any logic or services, there’s one question that comes first: security.

Breaking down what was wrong with the old architecture and how I redesigned it: from a tree to two independent clusters, zero trust, one domain per cluster, and Docker-based onboarding.

Last autumn I lost my VPN. A story about the patterns that kill services, the arms race between regulators and protocols — and why all of it is ultimately about people.

Why a private network is first and foremost a social structure, how it grows from the bottom up, and why freedom of communication should be a norm — not a privilege.

A prophetic article from Habr I couldn’t find again — and the arms race it predicted. From OpenVPN to statistical invisibility.

The technical side of the project hasn’t been standing still — I structured the data, chose storage formats, and laid the groundwork for future automation.

What KV stores are, why they matter for distributed systems, and how etcd became the foundation of operational data storage in Sigil Gate.