Projects
Each page covers the problem, my role, the architecture, the decisions and their trade-offs, and how the result was verified. Labels say whether something is a personal project, professional work or a design that has not been built yet.
Kubernetes clusters and the platform services around them, built to be rebuilt.
A browser-based network lab. Draw a topology, cable ports in a rack, deploy it with Containerlab and configure every device from a browser terminal.
A parameterized runbook that takes a bare Rocky Linux host to a healthy three-node Talos cluster, rebuilt from scratch until every silent failure was written down.
Overlay networks, tenant isolation and access control, from VXLAN to RBAC.
Private, isolated tenant networks stretched across separate dedicated servers, with SONiC running BGP and VPP doing VXLAN, gateways and ACLs. Validated path by path.
A proposed access model for a cluster shared through one admin kubeconfig. Per-user identities come first and OIDC groups later, with roles that never need rewriting.
Pipelines, runners and the gates that decide what reaches production.
How I build and run delivery pipelines, shown through a GitLab pipeline for a TypeScript monorepo, a self-hosted runner, and the Jenkins and quality-gate work around them.
Professional projects are described without client-confidential names, host names, addresses or configuration. Diagrams are redrawn from the source documents, and excerpts are rewritten rather than copied. Some of my work, such as the Jenkins setup on client infrastructure, has no public artifact at all, so it appears as scope in the CI/CD case study and under experience.