-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🌱 Migrate gcr.io/kubernetes-ci-images to gcr.io/k8s-staging-ci-images #4107
🌱 Migrate gcr.io/kubernetes-ci-images to gcr.io/k8s-staging-ci-images #4107
Conversation
Hi @fmuyassarov. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/cc @fabriziopandini |
test/framework/kubernetesversions/data/debian_injection_script.envsubst.sh
Outdated
Show resolved
Hide resolved
/ok-to-test |
/retest |
@vincepri Do I have to re-generate bindata to pass verify? |
yes, because this PR is changing a script that is embedded as bin data |
95654db
to
2441437
Compare
Thank you. Done. |
/retest |
@furkatgofurov7 |
2441437
to
c34e2d1
Compare
@vincepri this should be good to go I think. |
/lgtm |
/lgtm |
Should we also change this to /k8s-release-dev here? cluster-api/test/framework/kubernetesversions/data/debian_injection_script.envsubst.sh Line 84 in a597f9e
|
Yes, initially we tried to migrate https://storage.googleapis.com/kubernetes-release-dev to https://storage.googleapis.com/k8s-release-dev but then as @neolit123 commented in #4103 (comment) the latest artifacts weren't available in GCS bucket. |
the CI job that is responsible for pushing artifacts to the new GCS is failing: |
Is that problem fixed now? If so, we should change over now I think. |
the GCS problem is fixed, but we found a problem with the ci/latest marker and the GCR: |
potential fix for the new GCR problem: |
/retitle 🌱 Migrate gcr.io/kubernetes-ci-images to gcr.io/k8s-staging-ci-images |
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.
@neolit123 @justaugustus Seems the linked PR in test-infra has been merged, please feel free to unhold if we're ready to merge
/approve
/hold
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vincepri 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 |
who is going to own backporting this to v1alpha3? |
I am happy to do it @CecileRobertMichon . |
/lgtm |
Here is the backport to release-0.3 branch: #4143 |
/retest |
/test pull-cluster-api-test-main |
What this PR does / why we need it:
Migrate gcr.io/kubernetes-ci-images to gcr.io/k8s-ci-images
Which issue(s) this PR fixes:
Fixes #4103