Repeatable rebuilds
The cluster can be destroyed and reconstructed without undocumented manual intervention.
Selected work
My portfolio centers on infrastructure that can be inspected, rebuilt, operated, and tested. The repository is part of the deliverable: architecture, automation, procedures, and failure recovery all matter.
A three-node Kubernetes platform on Proxmox engineered as a real operations environment. The goal is not simply to host applications—it is to practice provisioning, hardening, observability, recovery, and continuous reconciliation as one cohesive system.
System design
Each tool has a bounded responsibility. That separation keeps the rebuild path understandable and makes failures easier to localize.
Defines virtual machines, compute, storage, networking, and placement across the Proxmox cluster.
Builds a repeatable Fedora node baseline, installs the container runtime, and applies system hardening.
Continuously reconciles controllers, configuration, and applications from version-controlled desired state.
Exposes cluster health and workload behavior through metrics, dashboards, and actionable signals.
What the project demonstrates
The cluster can be destroyed and reconstructed without undocumented manual intervention.
Platform health is evaluated through telemetry and explicit verification—not visual assumptions.
Node failures, recovery paths, and backup assumptions are tested as engineering requirements.
Procedures, architecture decisions, and incident lessons live alongside the implementation.
Application delivery
The site is statically built with Astro, packaged in a hardened unprivileged container, published to GHCR, pinned by digest, and reconciled into Kubernetes by Flux. Traefik and cert-manager complete the public delivery path.
Technology