3b000e1ab1
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> |
||
|---|---|---|
| .. | ||
| k3s-upgrade | ||
| networking | ||
| scripts | ||
| CLUSTER_ACCESS.md | ||
| K3S_OPERATIONS.md | ||
| README.md | ||
Infrastructure
This directory contains cluster-wide infrastructure configurations that support all applications.
Structure
networking/
Network-level configurations including:
- Network Architecture - Comprehensive network architecture documentation
- DNS Requirements - DNS records and configuration guide
- Ingress controller configurations (Traefik)
- Network policies
- Load balancer configurations (k3s ServiceLB)
- Certificate management (cert-manager, TLS)
- Certificate reloading (Stakater Reloader)
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:
- Test thoroughly before applying
- Document all changes
- Consider the impact on existing deployments
- Coordinate with other team members
Adding Infrastructure Components
When adding new infrastructure components:
- Create appropriate subdirectories if needed
- Include clear documentation
- Define dependencies and prerequisites
- Provide rollback procedures
- Update this README with the new component