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
e2e/storage-csi: replace gcr.io/gke-release to the community registry k8s.gcr.io/sig-storage #98805
Conversation
@cpanato: This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
args: | ||
- "--v=5" | ||
- "--csi-address=/csi/csi.sock" | ||
volumeMounts: | ||
- name: socket-dir | ||
mountPath: /csi | ||
- name: csi-resizer | ||
image: gcr.io/gke-release/csi-resizer:v0.5.0-gke.0 | ||
image: k8s.gcr.io/sig-storage/csi-resizer:v0.5.0 |
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.
I saw there is updated images v0.5.1
and even v1.1.0
https://github.com/kubernetes/k8s.io/blob/master/k8s.gcr.io/images/k8s-staging-sig-storage/images.yaml#L28-L35
should we update to use the path release or upgrade to 1.1.0?
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.
Yeah upgrading to 1.1.0 is fine, thanks!
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.
/hold
To address this
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.
done @spiffxp PTAL
how we will deal with this image gcr.io/gke-release/gcp-compute-persistent-disk-csi-driver:v1.0.1-gke.0
per my comment #98805 (review)
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.
upgrading to 1.1.0 looks like now we have some timeouts :/
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.
looks like does not exist in the community registry here this is built? or it is easier to just copy to the new registry?
871296f
to
1a8cd80
Compare
/priority important-soon |
/test pull-kubernetes-bazel-test |
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.
/approve
args: | ||
- "--v=5" | ||
- "--csi-address=/csi/csi.sock" | ||
volumeMounts: | ||
- name: socket-dir | ||
mountPath: /csi | ||
- name: csi-resizer | ||
image: gcr.io/gke-release/csi-resizer:v0.5.0-gke.0 | ||
image: k8s.gcr.io/sig-storage/csi-resizer:v0.5.0 |
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.
Yeah upgrading to 1.1.0 is fine, thanks!
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.
Will lgtm once hold is address
args: | ||
- "--v=5" | ||
- "--csi-address=/csi/csi.sock" | ||
volumeMounts: | ||
- name: socket-dir | ||
mountPath: /csi | ||
- name: csi-resizer | ||
image: gcr.io/gke-release/csi-resizer:v0.5.0-gke.0 | ||
image: k8s.gcr.io/sig-storage/csi-resizer:v0.5.0 |
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.
/hold
To address this
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato, msau42, spiffxp The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
… k8s.gcr.io/sig-storage
1a8cd80
to
c9ccfe6
Compare
/test pull-kubernetes-bazel-test |
/test pull-kubernetes-e2e-gce-csi-serial |
@cpanato: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
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.
/retest
/lgtm
/hold cancel
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Change the images used in the test from
gcr.io/gke-release
to use the community registry in this casek8s.gcr.io/sig-storage
Slack 🧵 https://kubernetes.slack.com/archives/C09QZFCE5/p1611747322028100
/assign @spiffxp @msau42
Which issue(s) this PR fixes:
Fixes partially kubernetes/k8s.io#1525
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: