fix: route CNB images through launcher on scheduler-k3s
Mirror the docker-local fix in #8525 for the k3s scheduler. CNB images default to a `/cnb/process/web` entrypoint that ignores incoming args, so non-web deployments, scheduled cron jobs, and ad-hoc `dokku run` / `cron:run` commands all need an explicit `launcher` entrypoint. The deployment and cron-job helm templates now set `command: [launcher]` when `image.type` is `pack`, and `TriggerSchedulerRun` sets the entrypoint to `launcher` for pack images while finishing the previously stubbed Procfile lookup branch so the resolved command is actually scheduled.
This commit is contained in:
@@ -75,6 +75,10 @@ spec:
|
||||
{{- range $config.args }}
|
||||
- {{ . }}
|
||||
{{- end }}
|
||||
{{- if eq $.Values.global.image.type "pack" }}
|
||||
command:
|
||||
- launcher
|
||||
{{- end }}
|
||||
envFrom:
|
||||
- secretRef:
|
||||
name: config-{{ $.Values.global.app_name }}
|
||||
|
||||
@@ -63,6 +63,10 @@ spec:
|
||||
{{- range $config.args }}
|
||||
- {{ . }}
|
||||
{{- end }}
|
||||
{{- if and (eq $.Values.global.image.type "pack") $config.args }}
|
||||
command:
|
||||
- launcher
|
||||
{{- end }}
|
||||
{{- if hasKey $config "web" }}
|
||||
env:
|
||||
- name: PORT
|
||||
|
||||
Reference in New Issue
Block a user