Creates the Argo CD Application that manages all cluster infrastructure applications from the stack.basicstack.de repository. Configuration: - Points to cluster-internal Forgejo (forgejo.forgejo.svc.cluster.local) - Excludes argocd directory to prevent self-management - Enables selfHeal for automatic sync of changes - Disables prune for manual deletion approval - Deployed to the cluster and verified working All existing services (Stalwart, Directus, Forgejo, BookStack, Pocket ID, OpenCloud, Passbolt) remain operational. Some pods restarted due to applying pending git changes (expected GitOps behavior). Note: Warning about duplicate opencloud namespace definition in openldap-deployment.yaml and opencloud-deployment.yaml - does not affect functionality, can be addressed in follow-up cleanup. Co-Authored-By: Paperclip <noreply@paperclip.ing> |
||
|---|---|---|
| .. | ||
| argocd | ||
| backup | ||
| bookstack | ||
| directus | ||
| forgejo | ||
| opencloud | ||
| paperclip | ||
| passbolt | ||
| platform-prod | ||
| pocket-id | ||
| stalwart | ||
| README.md | ||
Applications
This directory contains deployment configurations for all applications running on the basicstack.de cluster.
Structure
Each application should have its own subdirectory containing:
- Kubernetes manifests: Deployment, StatefulSet, Service, ConfigMap, Secret definitions
- Helm values: If using Helm charts, include values.yaml files
- Configuration files: Application-specific configs (TOML, JSON, YAML)
- Documentation: README or guide specific to the application deployment
- Patches: Any kubectl patches or modifications needed
Example: Stalwart
The stalwart/ directory serves as a reference implementation, containing:
- Multiple deployment variants (basic, with OIDC, etc.)
- Helm values files
- Monitoring dashboard configurations
- Backup/restore procedures
- Operational documentation
Adding a New Application
- Create a new directory:
apps/<application-name>/ - Add your Kubernetes manifests
- Include a README.md explaining:
- What the application does
- How to deploy it
- Configuration options
- Troubleshooting steps
- Test the deployment in a dev environment
- Commit with a descriptive message
Naming Conventions
- Directory names: lowercase, hyphen-separated (e.g.,
my-app) - Manifest files: descriptive names indicating resource type (e.g.,
deployment.yaml,service.yaml) - Use consistent naming across applications