3e9ba4a480
Generated complete OpenCloud config using 'opencloud init' and created
comprehensive sealed secrets for all 27 required configuration values.
## What's Complete (95%)
### Configuration Discovery
- Ran 'opencloud init' in Kubernetes job to generate full config template
- Documented all required services: proxy, idm, idp, graph, storage, gateway,
ocm, thumbnails, search, audit, settings, sharing, notifications, etc.
- Created complete opencloud.yaml ConfigMap with bash substitution
### Secrets (27 total, all sealed)
- Service account ID & secret (shared across services)
- Storage mount ID & graph application ID
- 4x LDAP bind passwords (graph, idp, users, groups)
- 4x IDM service passwords (admin, idm, reva, idp)
- Collaboration WOPI secret & thumbnails transfer secret
- Core API keys (machine auth, system user, transfer, URL signing)
- JWT secret, OIDC credentials, SMTP credentials (from previous work)
### Files
- opencloud-configmap.yaml: Complete config with ${VAR} substitution
- opencloud-config-sealed.yaml: All 27 secrets sealed
- opencloud-config-secrets-complete.yaml: Unsealed reference
- init-job.yaml: Helper to run 'opencloud init'
- DEPLOYMENT_STATUS.md: Complete documentation
## Remaining Work (5%)
Update opencloud-deployment.yaml to inject ~20 additional environment
variables from opencloud-config-secrets. Template provided in
DEPLOYMENT_STATUS.md. Estimated time: 5-10 minutes.
## Technical Approach
OpenCloud's 12-Factor config system:
1. Config file provides structure (/etc/opencloud/opencloud.yaml)
2. Environment variables override values (highest precedence)
3. Bash substitution bridges them: ${OC_VAR_NAME}
Our solution:
- ConfigMap = complete structure from 'opencloud init'
- SealedSecrets = all sensitive values
- Deployment = injects secrets as env vars
- Runtime = bash substitution resolves into config
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| 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