vnclagoon/vnctalk-prosody
14
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
158 Commits 2 Branches 0 Tags
main
Commit Graph
6 Commits
Author SHA1 Message Date
macanhhuy d6dddbbc91 chore: remove GCP + GitLab references, migrate to Gitea registry
Build + push image / build-and-push (push) Successful in 1m8s
Details 
Replace eu.gcr.io/vnc-development image refs with gitea.saas.vnc.biz/vnciac,
swap gcr-json-key pull secret for gitea-registry, and update CI/deploy docs
from GitLab CI to Gitea Actions.
 2026-08-19 17:31:05 +07:00
Stefan-Sanger b51bc373d3 fix: set non-LoadBalancer services to ClusterIP 
The http (5280), telnet (5582), and web2 (8080) Services were hardcoded
as NodePort, exposing them on every node's IP. Only s2s (5222/5269)
needs external exposure and remains LoadBalancer. Switch the three
internal services to ClusterIP so they are reachable only via ingress or
within the cluster. Also update the unused service.type value in
values.yaml to ClusterIP so NOTES.txt lands in the port-forward branch
instead of the stale NodePort branch.

Part-of: <http://gitlab.vnc.biz/uxf/vnctalk-prosody/-/merge_requests/3>
 2026-07-15 17:59:12 +02:00
Stefan-Sanger 1ed6a4c129 fix: keep DB migration hook logs inspectable after deployment 
Switch hook-delete-policy from hook-succeeded to before-hook-creation on
both the pre-upgrade and post-upgrade migration Jobs. hook-succeeded
deleted the Job immediately on success, making post-deploy log
inspection impossible. before-hook-creation keeps the most recent run's
Job and logs around (inspectable via kubectl logs job/<name>) and only
removes the previous Job when the next deployment fires the hook,
avoiding name conflicts and accumulation.

Part-of: <http://gitlab.vnc.biz/uxf/vnctalk-prosody/-/merge_requests/3>
 2026-07-15 17:59:12 +02:00
Stefan-Sanger e1c78e7358 feat: add pre-upgrade and post-upgrade DB migration hooks 
Dockerfile: add postgresql-client and bake db-customization/ SQL scripts
into the image at /vnc/db-customization/.

config/migrate.sh: detection + migration script with two modes:
- pre-upgrade: runs idempotent prosody-13-new-deployment.sql on 13.0.x
  databases; skips 0.11.6 (unsafe pre-upgrade) and new deployments.
- post-upgrade: waits for Prosody table, then runs the appropriate
  scripts — full 0.11.6->13.0.6 migration (rules-triggers + migration-once
  + new-deployment) or idempotent drift correction for 13.0.x.

Helm chart: two Job templates (db-migration-pre-upgrade.yaml,
db-migration-post-upgrade.yaml) gated by dbMigration.enabled (default
true). Both reuse the Prosody image and DB credentials from existing
values. backoffLimit: 0, hook-delete-policy: hook-succeeded.

Also tracks the db-customization SQL files (previously untracked, now
referenced by the Dockerfile ADD).

Part-of: <http://gitlab.vnc.biz/uxf/vnctalk-prosody/-/merge_requests/3>
 2026-07-15 17:59:09 +02:00
Stefan-Sanger e19cc05403 feat(helm): mount credentials from Secret and set per-container resources 
- chart: add secretEnv (existingSecret + keys) rendered as secretKeyRef in
  both containers; add resourcesProsody/resourcesSidecar defaults with
  dedicated requests and limits via a containerResources helper
- argo: move prosodyDBpass/fcmApiKey/fileShareSecret/avatarUploadPass out of
  env into secretEnv referencing a prosody-secrets Secret; set dedicated
  resource requests+limits per container
- argo: add prosody-secrets.example.yaml ArgoCD Application (with a warning
  to use Sealed Secrets / External Secrets / SOPS instead of plaintext)
- chart fixes: bump stale appVersion 0.11.6 -> 13.0.6; fix malformed service
  block in values.yaml

Part-of: <http://gitlab.vnc.biz/uxf/vnctalk-prosody/-/merge_requests/3>
 2026-07-15 17:58:02 +02:00
Stefan-Sanger 2ae1f8e480 import helm chart 
Part-of: <http://gitlab.vnc.biz/uxf/vnctalk-prosody/-/merge_requests/3>
 2026-07-15 17:58:02 +02:00