AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents
TypeScript ai-agentai-agent-toolsai-agentsai-agents-frameworkmcpmcp-servermcp-toolsmcpsn8n-alternativeno-code-automationworkflowworkflow-automationworkflows
fix(helm): pods only report ready when Activepieces can reach its database (#15947)
Bartosz Majewski96cf7d24b49d
diff --git a/.github/workflows/helm-chart.yml b/.github/workflows/helm-chart.ymlindex c1f8a94f059..ad590afb92a 100644--- a/.github/workflows/helm-chart.yml+++ b/.github/workflows/helm-chart.yml@@ -32,6 +32,7 @@ jobs:helm dependency buildhelm lint .helm template ap . | grep -q '^kind: Rollout'+ helm template ap . --show-only templates/deployment.yaml | yq -e '.spec.template.spec.containers[0] | (.livenessProbe.httpGet.path == "/api/v1/health" and .readinessProbe.httpGet.path == "/api/v1/health")'helm template ap . --api-versions apps/v1/StatefulSet | grep -q '^kind: StatefulSet'helm template ap . --set autoscaling.enabled=true --api-versions apps/v1/StatefulSet --api-versions argoproj.io/v1alpha1/Rollout > "$RUNNER_TEMP/rollout.yaml"grep -q '^kind: Rollout' "$RUNNER_TEMP/rollout.yaml"diff --git a/brain/knowledge/engineering/helm-chart.md b/brain/knowledge/engineering/helm-chart.mdindex 83b90f870bd..3334622846f 100644--- a/brain/knowledge/engineering/helm-chart.md+++ b/brain/knowledge/engineering/helm-chart.md@@ -36,6 +36,7 @@ Only two secrets, both `data: {}` with mittwald `secret-generator` annotations t- **The HPA targets whatever `activepieces.workloadType` resolves to.** It used to target a `Deployment` the chart never creates.- **`Chart.yaml` `appVersion` is the default image tag.** `release-self-hosted.yml` fails the release if it drifts from `package.json`, and the version sync PR bumps it.- **`AP_EDITION=ee` needs `AP_EXECUTION_MODE` set in the same breath or the pod will not boot.** `system-validator.ts` throws for `cloud`/`ee` in production unless the mode is one of `SANDBOX_PROCESS`, `SANDBOX_CODE_ONLY`, `SANDBOX_CODE_AND_PROCESS`, and the default is `UNSANDBOXED`. The error names the execution mode, not the edition, so it reads as a sandboxing problem rather than the edition switch that caused it.+- **Health checks need the `/api` prefix.** On a production app pod, `setNotFoundHandler` answers any non-`/api/` path without a file extension with the SPA `index.html` and a 200. So a probe or `helm test` on `/v1/health` or `/` passes as soon as the server listens and never reaches the database check behind `/api/v1/health` (503 when Postgres is unreachable).- **Bumping the bundled Bitnami subcharts is a database migration, not a version bump.** `postgresql` past 11.7.2 ships PostgreSQL 17, which will not start on the 14 data directory, so every bundled-DB install needs a dump, a fresh `data-<release>-postgresql-0` claim and a restore while the app is held at zero replicas (and HPA off). Plan it as its own release with migration docs. Images only exist under `bitnamilegacy/*` since Bitnami's 2025-08-28 freeze; check a target chart's default tags exist there first. See GIT-1929.- **OpenShift support is an overlay, not a default.** `values-openshift.yaml` moves the pod to non-root on 8080 without capabilities and turns off the bundled subcharts' security contexts (they hardcode user ID 1001); the base chart stays root on port 80 so `SANDBOX_PROCESS` installs keep working. The overlay must never set `runAsUser` / `fsGroup` (restricted-v2 rejects IDs outside the project's range) or `AP_EXECUTION_MODE` (the shipped values already read it from a secret, so it would render twice). See GIT-1929.- **An empty `persistence.storageClassName` keeps whatever class the live StatefulSet already has.** A StatefulSet's `volumeClaimTemplates` are immutable, so any change there fails the whole `helm upgrade` ("updates to statefulset spec ... are forbidden"). `activepieces.cacheStorageClassName` looks the old class up and reuses it; offline renders (Argo CD, `helm template`) cannot, so changing the chart's default class is a breaking change for them even though `helm upgrade` survives it.diff --git a/deploy/activepieces-helm/Chart.yaml b/deploy/activepieces-helm/Chart.yamlindex d71051a12f1..e236cd140e2 100644--- a/deploy/activepieces-helm/Chart.yaml+++ b/deploy/activepieces-helm/Chart.yaml@@ -16,7 +16,7 @@ type: application# This is the chart version. This version number should be incremented each time you make changes# to the chart and its templates, including the app version.# Versions are expected to follow Semantic Versioning (https://semver.org/)-version: 0.5.0+version: 0.6.0# This is the version number of the application being deployed. This version number should be# incremented each time you make changes to the application. Versions are not expected todiff --git a/deploy/activepieces-helm/templates/tests/test-connection.yaml b/deploy/activepieces-helm/templates/tests/test-connection.yamlindex cd076fee3ee..a401c5c1f63 100644--- a/deploy/activepieces-helm/templates/tests/test-connection.yaml+++ b/deploy/activepieces-helm/templates/tests/test-connection.yaml@@ -11,5 +11,5 @@ spec:- name: wgetimage: busyboxcommand: ['wget']- args: ['{{ include "activepieces.fullname" . }}:{{ .Values.service.port }}']+ args: ['{{ include "activepieces.fullname" . }}:{{ .Values.service.port }}/api/v1/health']restartPolicy: Neverdiff --git a/deploy/activepieces-helm/values.yaml b/deploy/activepieces-helm/values.yamlindex 0de64d77a41..5f35211bb08 100644--- a/deploy/activepieces-helm/values.yaml+++ b/deploy/activepieces-helm/values.yaml@@ -98,7 +98,7 @@ livenessProbe:periodSeconds: 10readinessProbe:httpGet:- path: /v1/health+ path: /api/v1/healthport: httpinitialDelaySeconds: 5periodSeconds: 5