lukevella/rallly-selfhosted
1
0
Fork 1
mirror of https://github.com/lukevella/rallly-selfhosted.git synced 2025-12-10 02:42:49 +01:00
Code

TLS, storage class, single replicas

Browse Source
This commit is contained in:
Gabriel Windlin 2025-12-01 15:57:21 +01:00
parent 3f8a67426e
commit dc0d543646
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
kubernetes/README.md
View File

@ -23,7 +23,9 @@ This directory contains base Kubernetes manifests to self-host Rallly. It separa
3. **Ingress (`ingress.yaml`):** 3. **Ingress (`ingress.yaml`):**
- Change `host: rallly.example.com` to your actual domain. - Change `host: rallly.example.com` to your actual domain.
- Ensure `ingressClassName` matches your cluster's controller (default is set to `nginx`). - Ensure `ingressClassName` matches your cluster's controller (default is set to `nginx`).
- **TLS:** Create the TLS certificate Secret named `rallly-tls` or enable cert-manager (see comments in `ingress.yaml` for options). - **TLS:**
- **Option 1 (Manual):** Create a TLS Secret: `kubectl create secret tls rallly-tls --cert=path/to/cert --key=path/to/key`
- **Option 2 (cert-manager):** See comments in `ingress.yaml` for automatic certificate provisioning setup.
## Deployment Order ## Deployment Order
@ -55,6 +57,8 @@ kubectl rollout restart deployment rallly
This performs a **rolling restart**, so there will be no downtime. However, ensure the new configuration is valid; if pods fail to start, check the logs with `kubectl logs -f deployment/rallly`. This performs a **rolling restart**, so there will be no downtime. However, ensure the new configuration is valid; if pods fail to start, check the logs with `kubectl logs -f deployment/rallly`.
**Note:** This assumes your Deployment has multiple replicas. If running a single Rallly instance (1 replica), there will be brief downtime during the restart.
## Verification ## Verification
Check that the pods are running: Check that the pods are running:
@ -69,6 +73,8 @@ The Postgres pod should show `1/1 Running` and the Rallly pod should eventually
The PostgreSQL StatefulSet requests a 1Gi PersistentVolume. Ensure your cluster has a default StorageClass configured, or update the `volumeClaimTemplates` in `postgres.yaml` to specify a StorageClass. If no StorageClass is available, the PersistentVolumeClaim will remain pending and the postgres pod will not start. Check your cluster's available StorageClasses with `kubectl get storageclass`. The PostgreSQL StatefulSet requests a 1Gi PersistentVolume. Ensure your cluster has a default StorageClass configured, or update the `volumeClaimTemplates` in `postgres.yaml` to specify a StorageClass. If no StorageClass is available, the PersistentVolumeClaim will remain pending and the postgres pod will not start. Check your cluster's available StorageClasses with `kubectl get storageclass`.
**Quick check:** Run `kubectl get storageclass` before deployment. If the output is empty, ask your cluster administrator to configure a default StorageClass, or update `postgres.yaml` to reference an existing one.
## Notes on Backups ## Notes on Backups
For production deployments, implement regular PostgreSQL backups. Consider using: For production deployments, implement regular PostgreSQL backups. Consider using: