antalos Documentation

antalos is a reusable template for hosting your own application stack and VMs, built from a Talos Kubernetes cluster, Debian application VMs, and an edge network. This handbook explains what you can use, where it runs, and how to build and maintain it from this repository.

01 / USEI want to use a serviceFind an application, sign in, and complete a first task. Follow official manuals for deeper product help. 02 / UNDERSTANDI want to understand the stackFollow traffic from the edge to an application, locate its data, and see what a failure affects. 03 / OPERATEI want to deploy or administer itPrepare dependencies, choose the right configuration files, and follow deployment and recovery runbooks.

Find what you need

Your task	Start here
Find an application and its guides	Service directory
Sign in or request access	Accounts and access
Learn how this repository is organized	Repository and ownership
Deploy antalos in another environment	Deployment path
Understand which services survive a failure	Availability and failure domains
Diagnose an unavailable application	Find the failing layer
Update these pages	Write and publish documentation

One repository, several deployment paths

Choose the owner before changing a service

1. Machines
   • Proxmox + OpenTofu
   • Talos and Debian guests
   • Home HAProxy pair
2. Workloads
   • Argo CD → Kubernetes apps
   • Ansible → Debian Compose
   • Cloud-init → Azure edge
3. Dependencies
   • Identity and public DNS
   • NFS and Garage objects
   • Credentials and backups

Each deployment path has its own configuration and lifecycle. A Git change reaches Kubernetes through Argo CD; VM playbooks and Azure provisioning follow separate procedures.

How to read the handbook

User guides explain tasks without requiring Kubernetes knowledge. Architecture guides describe the components and state behind those tasks. Admin guides connect repository files to deployment steps and operational decisions. Every service in the directory links to all three perspectives.

The guides describe the checked-in design. They do not report live health. Addresses identify the antalos environment; administrators deploying a fork must supply their own. Application values belong in apps/variables.yaml, while VM and Azure settings belong to their respective infrastructure projects.