Problem
The first testv4 qualification found three required workloads in ImagePullBackOff:
- channel proxy rendered
latest
- memory gateway rendered
0.1.0
- artifact service rendered
0.1.0
The exact qualified sha-f7d6771a4a5a075d424c7678d6165dd71c06b522 images exist for all three. The deploy engine currently applies the unified release tag only to a subset of enabled workloads and its rollout/verification gates omit these Deployments, including the cross-namespace artifact service.
Acceptance
- apply the qualified immutable release tag to every enabled first-party workload that participates in the release
- preflight the exact images before Helm mutation
- block successful completion until all required Deployments are available, including release-owned auxiliary namespaces
- keep completed Jobs from being reported as broken Pods
- cover the contract with executable tests
- update operator/package documentation
Evidence
Track F1 testv4 deployment of release 0.8.1 reached healthy TLS, database, server, UI, Cognee, LiteLLM and MCP, but these three mandatory Deployments remained unavailable because their rendered tags do not exist.
Refs #162
Problem
The first
testv4qualification found three required workloads inImagePullBackOff:latest0.1.00.1.0The exact qualified
sha-f7d6771a4a5a075d424c7678d6165dd71c06b522images exist for all three. The deploy engine currently applies the unified release tag only to a subset of enabled workloads and its rollout/verification gates omit these Deployments, including the cross-namespace artifact service.Acceptance
Evidence
Track F1 testv4 deployment of release 0.8.1 reached healthy TLS, database, server, UI, Cognee, LiteLLM and MCP, but these three mandatory Deployments remained unavailable because their rendered tags do not exist.
Refs #162