HomeInfra/HetznerTerra

Fork 0

Files

MichaelFisher1997 8b4a445b37

Deploy Cluster / Terraform (push) Successful in 31s

Details

Deploy Cluster / Ansible (push) Successful in 3m36s

Details

Update STABLE_BASELINE.md - CCM/CSI integration achieved

Document the successful completion of Hetzner CCM and CSI integration:
- CCM deployed via Ansible before workers join (fixes uninitialized taint)
- CSI provides hcloud-volumes StorageClass for persistent storage
- Two consecutive rebuilds passed all phase gates
- PVC provisioning tested and working

Platform now has full cloud provider integration with persistent volumes.

2026-03-23 02:25:00 +00:00

1.7 KiB

Raw Blame History

Stable Private-Only Baseline

This document defines the current engineering target for this repository.

Topology

1 control plane
2 workers
private Hetzner network
Tailscale operator access

In Scope

Terraform infrastructure bootstrap
Ansible k3s bootstrap with external cloud provider
Hetzner CCM deployed via Ansible (before workers join)
Hetzner CSI for persistent volumes (via Flux)
Flux core reconciliation
External Secrets Operator with Doppler
Tailscale private access
Persistent volume provisioning validated

Deferred for Later Phases

Observability stack (deferred - complex helm release needs separate debugging)

Out of Scope

HA control plane
public ingress or DNS
public TLS
app workloads
DR / backup strategy
upgrade strategy

Phase Gates

Terraform apply completes for the default topology.
k3s server bootstrap completes with external cloud provider enabled.
CCM deployed via Ansible before workers join (fixes uninitialized taint issue).
Workers join successfully and all nodes show proper providerID.
Flux source and infrastructure reconciliation are healthy.
CSI deploys and creates hcloud-volumes StorageClass.
PVC provisioning tested and working (validated with test pod).
External Secrets sync required secrets.
Tailscale private access works.
Terraform destroy succeeds cleanly or via workflow retry.

Success Criteria

✅ ACHIEVED - Two consecutive fresh rebuilds passed all phase gates with no manual fixes:

Build 1: Initial CCM/CSI deployment and validation (2026-03-23)
Build 2: Full destroy/rebuild cycle successful (2026-03-23)

The platform is now stable with cloud provider integration and persistent volume support.

1.7 KiB Raw Blame History