Skip to content

Wire startupProbe into workflows-backend and code-executor#306

Draft
marks wants to merge 2 commits into
mainfrom
add-startup-probe-workflow-code-executor
Draft

Wire startupProbe into workflows-backend and code-executor#306
marks wants to merge 2 commits into
mainfrom
add-startup-probe-workflow-code-executor

Conversation

@marks
Copy link
Copy Markdown

@marks marks commented Jun 4, 2026

Summary

  • The .Values.startupProbe block in values.yaml was previously only consumed by deployment_backend.yaml. This wires the same conditional into deployment_workflows.yaml and deployment_code_executor.yaml so the existing values apply uniformly across the main backend, workflows-backend, and code-executor.
  • No values.yaml changes — startupProbe.enabled still defaults to false, so this is a no-op for existing installs.
  • Bumps chart version 6.8.1 → 6.8.2.

Test plan

  • helm template with --set startupProbe.enabled=true renders startupProbe: blocks on all three deployments (backend port 3000, workflows-backend port 3000, code-executor port 3004).
  • Render diff review on CI kubeconform values.

🤖 Generated with Claude Code

marks and others added 2 commits June 4, 2026 16:32
The .Values.startupProbe block already existed in values.yaml but was
only consumed by deployment_backend.yaml. Mirror the same conditional
into the workflows-backend and code-executor deployments so the
existing values apply uniformly.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@marks marks marked this pull request as draft June 4, 2026 21:33
@marks marks marked this pull request as ready for review June 4, 2026 21:40
@marks marks marked this pull request as draft June 4, 2026 21:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant