Private Infrastructure Lab
Linux · k3s · networking · automation Linux / Dockerservices I run and troubleshoot Kubernetes / k3simportant learning and practice area Networking / NetBirdprivate service access and routing Monitoring / automationGrafana, Prometheus, Git and runbooksomnissa-horizon / former-vmware-horizon / vdi-environment
Together with a colleague, I helped build and maintain the VDI environment itself, not only support users on top of it.
- Omnissa Horizon / VDI environment, formerly VMware Horizon
- UAG and Connection Server setup and ongoing maintenance
- golden images, snapshots and image lifecycle work
- Veeam-backed backup paths for the surrounding infrastructure
- built before my daily AI workflow; easier to review and document with AI now
microsoft-365 / exchange / windows
Professional operations around Microsoft 365, Exchange and Windows infrastructure, with the focus on administration, support and service continuity.
- Microsoft 365 administration and user support
- Exchange support in operational environments
- Windows infrastructure troubleshooting under real constraints
incidents / handover / repeatable-fixes
Incidents usually start with incomplete information, so the work is to identify the affected layer, verify assumptions and keep the next step recoverable.
- operational support with real users waiting
- clear notes for handover and future investigation
- fixes that are understandable, not just lucky
professional-ops / responsibility
My strongest professional ground is operating, maintaining and documenting the systems around Horizon/VDI, Microsoft 365, Exchange and Windows infrastructure, with a practical bias toward service continuity.
linux / docker / pi-and-vps-services
The private lab is where Linux, Docker, Raspberry Pis, storage, backups and service exposure become real systems rather than abstract study topics.
- services operated across Raspberry Pi and VPS systems
- storage, backups and service exposure practiced on real services
kubernetes / k3s / workload-migration
Kubernetes is an active practical learning area: manifests, ingress, storage, rollouts, logs and failure states are tested against services I actually run.
- selected services moved from containers into k3s
- cluster access, logs, events and rollouts used for validation
netbird / monitoring / git-backed-notes
Private access, safe aggregate monitoring, Git-backed configuration and AI-assisted documentation turn experiments into something I can revisit, verify and improve.
- private access through NetBird instead of exposing admin paths
- Grafana, Prometheus and Git-backed notes used as verification tools
ai-assisted / human-validated
AI accelerates drafts and implementation. I provide context, review changes and validate them against the live systems.
sneak peek into my homelab-cluster
the terminal is animated and grabs 5-minute-cached data to display live (max age 5min)