c64f9ab0d0
Set up the repository structure following GitOps principles: - apps/ for application deployments (Stalwart as example) - infrastructure/ for cluster-wide configs (networking, monitoring) - docs/ for general documentation Migrated complete Stalwart deployment configuration including: - Multiple deployment variants (basic, OIDC-enabled) - Helm values files - Monitoring and dashboard configurations - Operational documentation (backup/restore, bootstrap) - Configuration patches and fixes Added comprehensive README files at each level to guide future use. Co-Authored-By: Paperclip <noreply@paperclip.ing>
41 lines
1.2 KiB
Markdown
41 lines
1.2 KiB
Markdown
# 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
|