-
Notifications
You must be signed in to change notification settings - Fork 554
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
deploy: use release repository for csi-resizer #4319
Conversation
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.
Thanks for the PR!
@Mergifyio queue |
🛑 The pull request has been removed from the queue
|
/test ci/centos/k8s-e2e-external-storage/1.27 |
/test ci/centos/k8s-e2e-external-storage/1.26 |
/test ci/centos/upgrade-tests-cephfs |
/test ci/centos/mini-e2e-helm/k8s-1.26 |
/test ci/centos/mini-e2e-helm/k8s-1.27 |
/test ci/centos/upgrade-tests-rbd |
/test ci/centos/k8s-e2e-external-storage/1.28 |
/test ci/centos/mini-e2e/k8s-1.26 |
/test ci/centos/mini-e2e/k8s-1.27 |
/test ci/centos/mini-e2e-helm/k8s-1.28 |
/test ci/centos/mini-e2e/k8s-1.28 |
The image is now available in the release repository and can be fetched from there instead of the staging repository. Signed-off-by: Sebastian Hoß <[email protected]>
argh my commit message was too long - I've pushed an update that is within the 80 chars limit. Sorry for the inconvenience.. |
Pull request has been modified.
@Mergifyio queue |
🛑 The pull request has been removed from the queue
|
/test ci/centos/upgrade-tests-cephfs |
/test ci/centos/k8s-e2e-external-storage/1.26 |
/test ci/centos/upgrade-tests-rbd |
/test ci/centos/mini-e2e-helm/k8s-1.26 |
/test ci/centos/mini-e2e/k8s-1.26 |
/test ci/centos/k8s-e2e-external-storage/1.27 |
/test ci/centos/k8s-e2e-external-storage/1.28 |
/test ci/centos/mini-e2e-helm/k8s-1.27 |
/test ci/centos/mini-e2e-helm/k8s-1.28 |
/test ci/centos/mini-e2e/k8s-1.27 |
/test ci/centos/mini-e2e/k8s-1.28 |
There is one failure that says
A successful run from yesterday does not have these errors in its log, however I'm not sure whether these errors are due to the change in this PR or caused by something else. @iPraveenParihar @nixpanic can you take another look? |
/test ci/centos/mini-e2e/k8s-1.26 |
@Mergifyio refresh |
✅ Pull request refreshed |
Describe what this PR does
According to https://github.com/kubernetes-csi/external-resizer/releases/tag/v1.9.2
registry.k8s.io/sig-storage/csi-resizer
is the release repository for the csi-resizer image. I'm guessing that #4132 used the staging repo because the image tag was not yet pushed to the release repo.Is there anything that requires special attention
I've verified that it is exactly the same image digest in both the staging and release repository, so this is basically a cosmetic change only.
Related issues
#4132 introduced the staging repo.
Future concerns
none afaics
Checklist:
Show available bot commands
These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:
/retest ci/centos/<job-name>
: retest the<job-name>
after unrelatedfailure (please report the failure too!)