Repository navigation
Report registry image references from container status - #4
Merged
Merged
Conversation
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.
CRI container discovery can return the image configuration hash as both image name and ID. That hash cannot be looked up as a manifest digest in ECR.
Read the image name and repository-qualified digest from the container-status request already used for process validation. Emit the digest reference as
recense.target.image.reference, retaining the runtime ID separately. No additional runtime calls or permissions are needed. Bare configuration hashes are not presented as registry references. Docker metadata remains unchanged.Prepare release 0.2.3. Tests cover the configuration/manifest distinction and event fields. Validation: Go race tests and vet, Helm lint, and independent adversarial review passed.