-
Notifications
You must be signed in to change notification settings - Fork 26
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
Check that the images we deploy are those we built #479
Comments
This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions. |
This is still relevant. |
|
Depends on docker/buildx#420 |
This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions. |
The issue this depended on upstream is now fixed, so this can be worked on. |
The id we get in docker image inspect sha256:41d0d1dc4ccf6d6d13e079fa17fd48aa633f3fe1e04550506770417a0a7d5d03 | jq -r '.[0].RepoDigests[0]' This will produce something like
and that can be compared with the $ kubectl get pods -A -l app=submariner-gateway -o json | jq -r '.items[].status.containerStatuses[].imageID'
localhost:5000/submariner-gateway@sha256:cc468fb364997c75fb57f8ff6889a5ac191ab088248bb0758e2e11f218a60b0d |
To avoid testing old images, instead of those we’re supposed to build, we should:
package/.image...
trackers)This can be made generic: we only need to check the
package
contents.The text was updated successfully, but these errors were encountered: