Skip to main content

Release 0.5.58 — CI Build Reliability (Native Per-Arch Images)

Sri Aradhyula
Sri Aradhyula
Sunny Whang
Sunny Whang

Released: 2026-07-22 Chart: oci://ghcr.io/cnoe-io/charts/ai-platform-engineering:0.5.58 Previous release: 0.5.57

Highlights​

0.5.58 is an internal CI reliability release with no application-facing changes: container image builds for arm64 now run on native ARM runners instead of QEMU emulation, fixing intermittent build timeouts and out-of-memory failures that were affecting release tagging.

Known issue: the mcp-webex container image failed to publish under this exact 0.5.58 tag due to a CI bug (see Known Issues below). If you use the Webex MCP server, pin mcp-webex to 0.5.57 or latest instead of 0.5.58 until you upgrade to a later release.

What's New​

Native per-arch image builds​

RAG images and the remaining 11 image-building CI workflows (agentgateway config bridge, OpenFGA authz bridge, Keycloak init, audit service, CAIPE UI, dynamic agents, MCP servers, scheduler, skill scanner, Slack bot, Webex bot) now build their arm64 variant on native ubuntu-24.04-arm runners instead of cross-building via QEMU emulation. QEMU emulation had started timing out or exhausting runner memory on heavier images (e.g. ingestors/default installing Chromium), causing release-tagging CI runs to fail. (#2272, #2274)

Bug Fixes​

  • workflow: corrected the release workflow's global status check so it accurately reflects whether all required jobs passed.

Breaking Changes​

No breaking changes. Drop-in upgrade from 0.5.57.

Known Issues​

mcp-webex image missing for the 0.5.58 tag. The [CI][MCP] MCP Servers Docker Build and Push workflow failed on this release's tag push: the manifest-merge step for mcp-webex errored with a digest "not found", caused by a digest-artifact naming collision across the 11 parallel MCP server image builds. Every other MCP server image (and every other service image in this release) published successfully — only mcp-webex:0.5.58 is affected.

  • The underlying bug was fixed in #2277 (fix(ci): disambiguate digest artifact patterns to prevent name-prefix collisions), but that fix landed in the 0.5.58-dev.2/0.5.58-dev.3 prereleases — after the 0.5.58 tag was already cut. It was never backported to republish the numbered 0.5.58 tag itself.
  • ghcr.io/cnoe-io/mcp-webex:0.5.58 does not exist. ghcr.io/cnoe-io/mcp-webex:latest is unaffected and currently points past this issue.
  • If your values.yaml pins mcp-webex to 0.5.58 explicitly, the image pull will fail. Pin it to 0.5.57 or latest instead, or wait for the next numbered release, which will include the fix.

Upgrade Guide: 0.5.57 → 0.5.58​

Overview​

Drop-in upgrade for every component except mcp-webex — no values.yaml edits required. This release is CI-tooling-only; no application code changed.

Helm Values Changes​

No Helm values changes between 0.5.57 and 0.5.58. Drop-in upgrade.

Upgrade Runbook​

1. Update chart version​

helm upgrade ai-platform-engineering \
  oci://ghcr.io/cnoe-io/charts/ai-platform-engineering \
  --version 0.5.58 \
  -f your-values.yaml

2. If you use the Webex MCP server​

Do not pin mcp-webex to 0.5.58 — that tag does not exist on ghcr.io. Keep it on 0.5.57 or latest:

mcpWebex:
  image:
    tag: "0.5.57"  # or "latest" — do not use "0.5.58"

All other component images are unaffected and safe to bump to 0.5.58.

3. Verify​

kubectl get pods -n <namespace>

Check that any pod using the mcp-webex image actually pulled and started — an ImagePullBackOff there is the symptom of this known issue.

Personal Impact Analysis​

No values.yaml changes required, aside from avoiding an explicit mcp-webex:0.5.58 pin as described above.

Full Values Diff​

No diff — values.yaml is identical between 0.5.57 and 0.5.58.