2026-07-01 18:08:31 +00:00
# Infrastructure
This directory contains cluster-wide infrastructure configurations that support all applications.
2026-08-09 15:55:39 +00:00
## Operational procedures (agent-facing)
- **[OS_UPDATE_PROCEDURE.md ](OS_UPDATE_PROCEDURE.md )** — weekly rolling Ubuntu OS update for all cluster nodes (drain → apt → reboot → verify → uncordon → cluster health → next). Never touches k3s config.
- **[OS_UPDATE_ROUTINE.md ](OS_UPDATE_ROUTINE.md )** — the Paperclip routine that fires the above weekly.
- **[K3S_OPERATIONS.md ](K3S_OPERATIONS.md )** — k3s version upgrades (separate concern from OS updates).
- **[ADD_WORKER_NODE.md ](ADD_WORKER_NODE.md )** — adding a worker node.
- **[CLUSTER_ACCESS.md ](CLUSTER_ACCESS.md )** — SSH / kubectl access.
2026-07-01 18:08:31 +00:00
## Structure
### `networking/`
Network-level configurations including:
Document k3s cluster network architecture and DNS requirements
Created comprehensive network documentation for BasicStack k3s cluster:
- NETWORK_ARCHITECTURE.md: Complete network architecture with diagrams,
node configuration, CNI (Flannel) details, ingress/LoadBalancer setup,
DNS configuration, TLS certificates, network policies, traffic flows,
and troubleshooting procedures
- DNS_REQUIREMENTS.md: Complete DNS record requirements for all services
including A records, MX records, SPF, DKIM, DMARC, and PTR records
- NETWORK_VERIFICATION.md: Verification report documenting current state
of all network components with findings and recommendations
Updated infrastructure README with links to new network documentation.
Key findings:
- All worker nodes correctly configured with --node-ip set to private IPs
- Flannel VXLAN properly configured with public IP annotations
- Traefik ingress controller operational
- 16/17 TLS certificates valid (registry-tls needs investigation)
- 3 LoadBalancer services properly configured
- Network policies securing database services
Addresses DEV-225: Verify and document k3s cluster network configuration
Related: DEV-224 (node-ip configuration), DEV-223 (DNS issues)
Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-07-06 20:04:46 +00:00
- **[Network Architecture ](networking/NETWORK_ARCHITECTURE.md )** - Comprehensive network architecture documentation
- **[DNS Requirements ](networking/DNS_REQUIREMENTS.md )** - DNS records and configuration guide
- Ingress controller configurations (Traefik)
2026-07-01 18:08:31 +00:00
- Network policies
Document k3s cluster network architecture and DNS requirements
Created comprehensive network documentation for BasicStack k3s cluster:
- NETWORK_ARCHITECTURE.md: Complete network architecture with diagrams,
node configuration, CNI (Flannel) details, ingress/LoadBalancer setup,
DNS configuration, TLS certificates, network policies, traffic flows,
and troubleshooting procedures
- DNS_REQUIREMENTS.md: Complete DNS record requirements for all services
including A records, MX records, SPF, DKIM, DMARC, and PTR records
- NETWORK_VERIFICATION.md: Verification report documenting current state
of all network components with findings and recommendations
Updated infrastructure README with links to new network documentation.
Key findings:
- All worker nodes correctly configured with --node-ip set to private IPs
- Flannel VXLAN properly configured with public IP annotations
- Traefik ingress controller operational
- 16/17 TLS certificates valid (registry-tls needs investigation)
- 3 LoadBalancer services properly configured
- Network policies securing database services
Addresses DEV-225: Verify and document k3s cluster network configuration
Related: DEV-224 (node-ip configuration), DEV-223 (DNS issues)
Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-07-06 20:04:46 +00:00
- Load balancer configurations (k3s ServiceLB)
2026-07-01 18:08:31 +00:00
- Certificate management (cert-manager, TLS)
Document k3s cluster network architecture and DNS requirements
Created comprehensive network documentation for BasicStack k3s cluster:
- NETWORK_ARCHITECTURE.md: Complete network architecture with diagrams,
node configuration, CNI (Flannel) details, ingress/LoadBalancer setup,
DNS configuration, TLS certificates, network policies, traffic flows,
and troubleshooting procedures
- DNS_REQUIREMENTS.md: Complete DNS record requirements for all services
including A records, MX records, SPF, DKIM, DMARC, and PTR records
- NETWORK_VERIFICATION.md: Verification report documenting current state
of all network components with findings and recommendations
Updated infrastructure README with links to new network documentation.
Key findings:
- All worker nodes correctly configured with --node-ip set to private IPs
- Flannel VXLAN properly configured with public IP annotations
- Traefik ingress controller operational
- 16/17 TLS certificates valid (registry-tls needs investigation)
- 3 LoadBalancer services properly configured
- Network policies securing database services
Addresses DEV-225: Verify and document k3s cluster network configuration
Related: DEV-224 (node-ip configuration), DEV-223 (DNS issues)
Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-07-06 20:04:46 +00:00
- Certificate reloading (Stakater Reloader)
2026-07-01 18:08:31 +00:00
### `monitoring/`
Observability infrastructure:
- Prometheus operator and configurations
- Grafana dashboards and datasources
- Logging stack (Loki, Promtail, etc.)
- Alert rules and notification channels
- Service monitors and pod monitors
## Purpose
Infrastructure configurations in this directory are shared across all applications. Changes here can affect the entire cluster, so:
1. Test thoroughly before applying
2. Document all changes
3. Consider the impact on existing deployments
4. Coordinate with other team members
## Adding Infrastructure Components
When adding new infrastructure components:
1. Create appropriate subdirectories if needed
2. Include clear documentation
3. Define dependencies and prerequisites
4. Provide rollback procedures
5. Update this README with the new component