Problem
The v0.2.2 Release Pipeline deployed the ambient-control-plane Deployment manifest (added in #1379) but has no build matrix entry for the component. The image quay.io/ambient_code/vteam_control_plane was never pushed to quay, so the pod is stuck in ImagePullBackOff on vteam-uat since the v0.2.2 release (2026-04-22 00:58 UTC).
Additionally, the deployment manifest uses :latest instead of the release version tag (v$TAG), unlike every other component.
Fix
- Add
ambient-control-plane to the build matrix in the Release Pipeline workflow (alongside frontend, backend, operator, etc.)
- Update
components/manifests/overlays/*/ambient-control-plane.yaml to use the versioned tag pattern consistent with other components
Affected files
.github/workflows/release-pipeline.yml (build matrix)components/manifests/overlays/*/ambient-control-plane.yaml (image tag)
Context
Discovered during investigation of vteam-uat outage on 2026-04-22. All three issues (#1378 + #1379 interaction) shipped together in v0.2.2.
Problem
The v0.2.2 Release Pipeline deployed the
ambient-control-planeDeployment manifest (added in #1379) but has no build matrix entry for the component. The imagequay.io/ambient_code/vteam_control_planewas never pushed to quay, so the pod is stuck in ImagePullBackOff on vteam-uat since the v0.2.2 release (2026-04-22 00:58 UTC).Additionally, the deployment manifest uses
:latestinstead of the release version tag (v$TAG), unlike every other component.Fix
ambient-control-planeto the build matrix in the Release Pipeline workflow (alongside frontend, backend, operator, etc.)components/manifests/overlays/*/ambient-control-plane.yamlto use the versioned tag pattern consistent with other componentsAffected files
.github/workflows/release-pipeline.yml(build matrix)components/manifests/overlays/*/ambient-control-plane.yaml(image tag)Context
Discovered during investigation of vteam-uat outage on 2026-04-22. All three issues (#1378 + #1379 interaction) shipped together in v0.2.2.