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.
Restore digest pinning for AWF 0.27.0 firewall sidecar images #38595
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
Restore digest pinning for AWF 0.27.0 firewall sidecar images #38595
Changes from all commits
00c5dc1f8dabacFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing
cli-proxydigest assertion inimageTagPartchecks:buildAWFImageTagWithDigestsunconditionally appendscli-proxy=sha256:...to the AWF imageTag whenever that pin is available — andcli-proxy:0.27.0is now embedded. The generatedimageTagfor v0.27.0 will be0.27.0,squid=...,agent=...,api-proxy=...,cli-proxy=..., but the test does not verify thecli-proxycomponent. A regression that droppedcli-proxyfrom the imageTag computation would go undetected.💡 Suggested fix
Add a sixth entry to the
imageTagPartslice:Note:
cli-proxyintentionally stays out ofexpectedPins(the manifest-header / pull-list check), becauseisCliProxyNeededis false for this test workflow. Only the AWF configimageTagfield needs the extra assertion.Uh oh!
There was an error while loading. Please reload this page.