-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
reintroduce ci-k8sio-backup job #17150
Conversation
This reverts commit a6a2655. The backup job has received some optimizations in kubernetes/k8s.io#677, In addition, the k8s-artifacts-prod-bak GCR has been manually pre-populated with all ~30K images in k8s-artifacts-prod for all ASIA, EU, and US regions, which will result in jobs taking just minutes to run (as subsequent runs are mostly NOP runs). For more discussion on the backup job, please see https://docs.google.com/document/d/11eiosJvm2xEVUhPRU3-luANxxTPL5FqQdJXVrLPImyQ/edit?usp=sharing.
See kubernetes/k8s.io#718 for binding the KSA to the k8s-infra-gcr-promoter@k8s-artifacts-prod-bak.iam.gserviceaccount.com account referenced in this PR.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: listx, 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 |
/hold cancel |
@listx: Updated the
In response to this:
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 distinctly recall @fejta saying that the SA will get auto-deployed on merge. It's a bit moot as you answered your own question but I just thought I'd share for the record, albeit belatedly. |
Strange, despite what I just posted, the job is showing an error that it cannot find the service account:
Maybe some manual intervention is required? @spiffxp |
Hmm, it looks like the latest job ran successfully at ~4AM. I guess it was just a config timing (or deployment timing) issue. Thanks! |
This is blocked on kubernetes/k8s.io#718.
/assign @spiffxp