You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(hosting): fail the upgrade when secrets.existingSecret is missing keys
When secrets.existingSecret is set the chart generates nothing and reads
every application and control-plane key from that Secret. A chart version
that starts consuming a new key therefore breaks the webapp rollout with a
CreateContainerConfigError partway through, leaving the release half-applied.
The pre-install/pre-upgrade validation now looks the Secret up and fails with
the full list of missing keys, so a running release is left untouched. The
lookup returns nothing under helm template and client-side dry-run, where the
check is skipped rather than guessing.
{{- fail (printf "Secret %q (secrets.existingSecret) is missing required keys: %s. Add them before upgrading - while secrets.existingSecret is set the chart generates nothing and inline secrets.* values are ignored. See https://trigger.dev/docs/self-hosting/kubernetes#upgrading" .Values.secrets.existingSecret (join ", " $missing)) }}
84
+
{{- end }}
85
+
{{- end }}
86
+
{{- end }}
58
87
59
88
{{/*
60
89
This template produces no output but will fail the deployment if validation fails
0 commit comments