Projects

GitHub-based development and deployment workflows are being implemented to build hands-on experience with modern source control, CI/CD practices, automated deployment, and infrastructure change management.

The portfolio website itself serves as an initial implementation, with code developed locally, committed to GitHub, and automatically deployed to Vercel.

The AI Network Agent project is intended to create an assistant capable of understanding the architecture and documentation of the home lab.

Initial capabilities will focus on answering questions about the environment and retrieving infrastructure documentation.

Future stages may incorporate monitoring and observability information, health analysis, network status, incident summaries, and controlled operational workflows.

Any future ability to execute infrastructure changes will be separated through authenticated automation layers rather than giving an AI system unrestricted direct access to network devices or virtualization platforms.

Proxmox High Availability is planned as a future infrastructure project.

The current environment operates as a five-node Proxmox cluster, but cluster membership alone does not mean workloads automatically restart on another node when a host fails.

The HA project will evaluate which workloads actually require automatic recovery rather than enabling HA indiscriminately for every virtual machine and container.

The project will include reviewing shared-storage requirements, workload dependencies, network availability, node capacity, quorum behavior, migration capability, and recovery priorities.

Selected services will then be configured and tested for automatic recovery following simulated node failures.

The objective is to build a deliberate HA architecture based on service criticality rather than simply enabling a feature.

Kubernetes is planned as a future learning and infrastructure project rather than a current production dependency.

The initial goal is to build a small K3s cluster on top of the existing Proxmox environment and gain practical experience with container orchestration, service discovery, ingress, persistent storage, cluster networking, and application resiliency.

The project can later incorporate Helm, Git-based deployment workflows, observability, and controlled CI/CD integration.

Kubernetes will be introduced because it adds useful orchestration and platform-engineering experience, not because the current Docker-based services require unnecessary migration.

Infrastructure as Code is a major part of the next phase of the lab rather than a minor tooling exercise.

The target operating model is GitHub as the source-control and change-history layer, Ansible for configuration management, Terraform or OpenTofu for declarative infrastructure provisioning, Docker Compose for repeatable application stacks, and GitHub Actions for controlled CI/CD workflows.

The objective is to reduce manual configuration, improve repeatability, make changes reviewable, and create a clear path from documented intent to deployed infrastructure.

Public repositories will contain sanitized examples and portfolio documentation, while operational configuration containing internal addressing, ports, hostnames, topology mappings, or other sensitive environment details will remain private.

Passwords, API tokens, private keys, and other secrets will not be committed to Git repositories.

Monitoring and observability will continue to mature beyond basic availability checks.

Planned work includes stronger metric collection, centralized logging, dashboards, alerting, historical performance analysis, and event correlation across networking, compute, storage, and applications.

Additional projects will continue to expand the environment across infrastructure automation, security, DevOps, AI, resilience, monitoring, observability, configuration management, and disaster recovery.

The lab is intentionally treated as an evolving platform rather than a finished collection of applications.