stack.basicstack.de/infrastructure
Paperclip CTO 27d26fb11b Document DNS configuration and service CIDR fix
- Fixed Service CIDR documentation (10.96.0.0/16, not 10.43.0.0/16)
- Added comprehensive DNS configuration guide
- Documented kubelet cluster-dns requirements
- Added CoreDNS forward configuration details
- Documented DNS CIDR mismatch troubleshooting (DEV-223)

Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-07-06 18:22:53 +00:00
..
k3s-upgrade Add k3s cluster management automation and documentation 2026-07-06 17:08:21 +00:00
networking Document DNS configuration and service CIDR fix 2026-07-06 18:22:53 +00:00
scripts Add k3s cluster management automation and documentation 2026-07-06 17:08:21 +00:00
CLUSTER_ACCESS.md Update k3s cluster documentation 2026-07-06 17:54:53 +00:00
K3S_OPERATIONS.md Document DNS configuration and service CIDR fix 2026-07-06 18:22:53 +00:00
README.md Initialize CD/CI repository structure with Stalwart example 2026-07-01 18:08:31 +00:00

Infrastructure

This directory contains cluster-wide infrastructure configurations that support all applications.

Structure

networking/

Network-level configurations including:

  • Ingress controller configurations
  • Network policies
  • DNS settings
  • Load balancer configurations
  • Certificate management (cert-manager, TLS)
  • Service mesh configurations (if applicable)

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