Why it mattered
It matters because it shows initiative. No one assigned this project to me. I built it to sharpen how I think about deployment, networking, service management, and the reality of maintaining systems over time.
Infrastructure / Self-Directed Learning
A two-node Raspberry Pi k3s cluster built to learn infrastructure by operating it directly.
The lab exists because I learn best by building systems from scratch and living with their constraints. It is a deliberately small environment, but it represents the way I like to close the gap between theory and working infrastructure.
Why it mattered
It matters because it shows initiative. No one assigned this project to me. I built it to sharpen how I think about deployment, networking, service management, and the reality of maintaining systems over time.
Role
Designed, assembled, configured, and maintained the cluster, including service deployment, SSH access, and remote administration.
Constraints
System approach
Set up a two-node Raspberry Pi cluster running k3s as a compact but real Kubernetes environment.
Deployed and managed containerized applications through Kubernetes manifests and routine operational checks.
Configured SSH and network access for remote administration, giving the setup enough permanence to stay useful as a learning tool.
Outcomes
What it says about me
This project says something quieter but important about me: I will get my hands dirty to understand a system properly, especially when I know it connects to larger ambitions later.
Keep exploring
Automation / Observability
Built around n8n, messaging integrations, GitHub Actions context, diagnostics, and guardrailed operations workflows, then discussed publicly on Teller’s Tech.
Backend / Cloud / Delivery
A sanitized view of backend systems, AWS redesign, CI/CD, messaging operations, and cross-functional delivery leadership.