Qb8s Infrastructure — A Technical Workbench
Personal infrastructure for software development, experimentation and hosting self-managed services.
Overview
Qb8s is a personal engineering environment for exploring infrastructure and running self-hosted services. It provides a place to connect software development with the operational work needed to keep systems useful.
Areas of exploration
- Kubernetes and k3s for service orchestration
- ArgoCD for declarative deployment workflows
- Docker for reproducible application packaging
- PowerDNS and reverse proxies for service discovery and routing
- Azure and CI/CD for connecting code changes to deployments
Engineering principles
Prefer a configuration that can be explained and reproduced. Automate repeated operations, keep ownership clear and make recovery part of the design.
Not every experiment needs to become permanent infrastructure. The useful outcome can be a better understanding of a tradeoff rather than another running service.
What these notes cover
This is an ongoing technical workbench. These notes outline its scope; specific deployment details and verified operational lessons can be documented as the work develops.
The application projects provide concrete examples of the infrastructure concerns:
- From Azure Pipelines to Argo CD describes the separation between application builds and deployment configuration in Culina and Elysion.
- Connecting Client Errors to Backend Diagnostics follows the observability concerns around a web-to-API workflow.
- Modular Boundaries Without Microservices explores how application structure and deployment choices relate.