AUGUST 2026
Platform Documentation, Sanitization, and Guarded Publishing
The portfolio had grown into a public representation of a real operating environment, which meant documentation accuracy and information disclosure needed to be treated as engineering concerns rather than cosmetic website work. This phase established a sanitized current-state platform view, separated deployed capabilities from planned work, and added a guarded PowerShell publishing workflow that validates the repository before promotion to production.
JULY 2026 · GITOPS
Bootstrapping GitOps Storage and the First Application
After the Kubernetes cluster became healthy, the next problem was how to operate it repeatably. This phase established Argo CD, an app-of-apps structure, Helm-driven deployments, dynamic persistent storage, Uptime Kuma, and an initial operational alerting path.
JULY 2026 · KUBERNETES
Kubernetes Cluster Bootstrap and Cilium Validation
A three-node Kubernetes environment was built from Ubuntu virtual machines using containerd, kubeadm, Helm, and Cilium. The work focused not only on reaching a running state, but on validating the runtime, networking, node behavior, and architectural decisions behind the cluster.
JULY 2026 · ZERO TRUST / REMOTE ACCESS
Tunnel-in-a-Tunnel
A remote-access troubleshooting case study involving Cloudflare Zero Trust, Cloudflare Tunnel, Apache Guacamole, and Windows RDP. The failure was traced through each layer of the access path and the design was simplified without reopening direct inbound access.
JOURNAL STANDARD
Document implemented work, not imagined architecture.
Journal entries are written after meaningful implementation, troubleshooting, or validation work. Planned capabilities can be discussed as future work, but they are kept visibly separate from the current state of the platform.