Repository navigation
chore(platform): release 2.5.6 (zelkor verify finds digest-pinned images) - #141
Merged
Merged
Conversation
On containerd (k3s) a pod that pins its image by digest reports status.image as the bare config digest (sha256:...), so verify matched no Zelkor image and printed "no Zelkor images running" on a production-shaped install. The image now comes from the pod spec, then the status, then the repository in imageID. Live on a k3s cluster running the signed 2.5.5 release: 10/10 checks for 5 Zelkor images (before: nothing verified). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ges) - charts, first-party image tags, Zelkor Dockerfile bases and example charts at 2.5.6; example chart dependencies rebuilt - profiles/values-production.yaml at tag 2.5.6, digests empty until the signed release run - THIRD_PARTY_NOTICES: 2.5.6 row (no third-party changes) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2.5.6 changes only the zelkor CLI (verify image resolution); no image, chart or runtime behaviour changes, so the 2.5.5 S-gate run stands. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Release 2.5.6 (PATCH):
zelkor verifyfound no Zelkor images on a digest-pinned install.On containerd (k3s) a pod that pins its image by digest reports
status.imageas the bare config digest (sha256:…), soverifymatched nothing and printed "no Zelkor images running" on exactly the production layout (profiles/values-production.yamlpins digests). The image now comes from the pod spec, then the status, then the repository inimageID.Verification
zelkor --env <k3s lab> verify zelkor-platformagainst the signed 2.5.5 releaserelease-evidence/v2.5.6-ce): no image, chart or runtime change🤖 Generated with Claude Code