-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Fix: Skaffold reloads unchanged, existing image again into the cluster #4983
Conversation
Codecov Report
@@ Coverage Diff @@
## master #4983 +/- ##
==========================================
+ Coverage 72.27% 72.28% +0.01%
==========================================
Files 361 361
Lines 12640 12670 +30
==========================================
+ Hits 9135 9159 +24
- Misses 2827 2830 +3
- Partials 678 681 +3
Continue to review full report at Codecov.
|
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.
This change looks good to me and makes sense. We shd ship this change
However, i am not sure how it fixes #4955.
From the issue logs looks like we were checking a tag "eu.gcr.io/tools-org-veroo/party-service:d46578239dd325395e15e8ab16a2c499616a15e662ed196c18549e8d2bea38b6" which exist in the kubectl get nodes -o jsonpath='{@.items[*].status.images[*].names[*]}
am i missing something obvious?
@tejal29 You're right. My bad I missed it in the description. It looks like I faced with another issue. |
But also I was unable to fully reproduce the bug described here, perhaps due to a lack of information. |
Related: #4955
Description
the command
kubectl get nodes -ojsonpath = '{@.items[*].status.images[*].names[*]}'
returns a list with normalized image refs. The returned image may differ fromartifact.Tag
. This PR adds image normalization before checking already loaded images.