Files

T

History

keyhan 54ab2f2f05 Fix Kaniko registry auth and push target for Harbor builds.

Mount docker config as config.json (Kaniko requirement), push via
harbor-registry internal URL, and wire harbor_registry_user credentials
in Helm/GitOps values.

Co-authored-by: Cursor <cursoragent@cursor.com>

2026-07-10 12:29:23 +03:30

migrations

fix(platform): apply production hardening from audit plan

2026-07-02 19:35:07 +03:30

templates

Fix Kaniko registry auth and push target for Harbor builds.

2026-07-10 12:29:23 +03:30

.helmignore

Add cloudhost-platform Helm chart and registry ingress manifests.

2026-05-24 19:01:05 +03:30

Chart.yaml

Add cloudhost-platform Helm chart and registry ingress manifests.

2026-05-24 19:01:05 +03:30

README.md

Add cloudhost-platform Helm chart and registry ingress manifests.

2026-05-24 19:01:05 +03:30

values-images.yaml

Add cloudhost-platform Helm chart and registry ingress manifests.

2026-05-24 19:01:05 +03:30

values-production.example.yaml

fix(build): default Kaniko and init images to Harbor via Helm values

2026-07-03 14:20:36 +03:30

values.yaml

Fix Kaniko registry auth and push target for Harbor builds.

2026-07-10 12:29:23 +03:30

README.md

cloudhost-platform

Helm chart for the CloudHost control plane: backend API, frontend UI, PostgreSQL, and Redis.

Quick install

helm upgrade --install cloudhost . \
  -n cloudhost --create-namespace \
  -f values-production.example.yaml

Ingress / TLS

Value	Description
`ingress.enabled`	Create Ingress resources
`ingress.tls.enabled`	Enable cert-manager TLS
`ingress.tls.clusterIssuer`	ClusterIssuer name (e.g. `letsencrypt-prod`)
`ingress.frontend.host`	UI hostname
`ingress.api.host`	API hostname

Requires NGINX Ingress Controller and cert-manager when TLS is enabled.

Frontend image

Build with the public API URL baked in:

docker build -t $REG/cloudhost-frontend:tag \
  --build-arg NEXT_PUBLIC_API_URL=https://api.platform.example.com \
  ../../frontend

Migrations

SQL files in migrations/ run via a post-install/post-upgrade Job when migrations.enabled is true. They assume incremental schema changes on top of an existing database; for a completely empty database you may need to bootstrap schema first (e.g. one-time NODE_ENV=development or manual setup).