Skip to content

docs(agent-collab): document sideload tag aliasing trap and two exits#225

Merged
weicao merged 1 commit into
mainfrom
docs/sideload-tag-aliasing
May 19, 2026
Merged

docs(agent-collab): document sideload tag aliasing trap and two exits#225
weicao merged 1 commit into
mainfrom
docs/sideload-tag-aliasing

Conversation

@weicao
Copy link
Copy Markdown
Contributor

@weicao weicao commented May 18, 2026

Summary

  • Add a Sideload + tag 别名陷阱 section to docs/agent-collab/addon-patch-image-build-handoff-roles-guide.md.
  • Explain why a sideloaded patch image can appear under an older tag in pod status when multiple tags point to the same digest.
  • Document two exits: remove stale runtime tag aliases, or pin the chart image by digest.

Why

Addon teams sometimes sideload controller patch images when registry push is unavailable. If the node runtime keeps both the base tag and patch tag for the same digest, kubelet may surface either tag in pod.status.containerStatuses[*].Image. With tag-only specs, InstanceSet strict tag-string comparison can then keep the InstanceSet from marking ready even when the running image data is the intended patch digest.

Test plan

  • git diff --check origin/main...HEAD
  • Section stays inside the existing patch-image handoff guide; no new duplicate guide.
  • PR body, commit message, and changed docs public-hygiene grep clean.

…mage handoff guide

When sideloading a patch container image into a node where the same
image already had another tag (typically a base tag), the runtime keeps
both tags pointing at the same digest. kubelet may report any of those
tags on pod status.Image, not necessarily the tag in PodSpec. With a
chart that references the image by tag, this causes
InstanceSet controller's strict tag string comparison in
isImageMatched to fail, and the InstanceSet does not mark ready, even
though the running image data is correct.

Document the trap and the two operational exits:

1. Drop the base/old tag alias from the runtime so the patch tag is the
   only tag kubelet can surface (e.g. ctr -n k8s.io image rm <old-tag>).
2. Pin the chart image reference to a digest. InstanceSet controller's
   main-branch isImageMatched already consults status.ImageID as the
   canonical digest source for digest-pinned specs.

Either exit closes via the existing pod imageID equals build sha
verification rule, not via 'pod is up'.
@weicao weicao merged commit 224f07d into main May 19, 2026
@weicao weicao deleted the docs/sideload-tag-aliasing branch May 19, 2026 05:37
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