-
Notifications
You must be signed in to change notification settings - Fork 497
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
k8s.gcr.io VDF (Vanity Domain Flip): Move official container images to K8s Infra #270
Comments
Yep, this is something that @timstclair and I are looking into. |
We're expecting to have a proposal out in the next week or two that will address this. |
Please include me. We have internal infrastructure that handles the replication of |
Please include me as well, I have been thinking about this for some time as well, but haven't just had the time to focus fully on trying to make a change here (not that I have the permissions to do so either but 😄) |
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
Progress: kubernetes/kubernetes#54174 /remove-lifecycle stale What are the next steps here? |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Add features archives for past releases (1.3 - 1.11)
I really hope this will happen in the coming months. Check out this issue for high-level updates, but also updates to the Or, please attend the wg-k8s-infra meetings where updates to this work is currently on the agenda. |
/assign @tpepper @justaugustus @timothysc @dims |
@listx -- Would you mind providing an update on your side as we're nearing the date? |
I'm manually performing the backups for now to make the automated jobs not time-out and cause a quota exceeded error. The backup optimization implementation has hit a snag with Workload Identity here kubernetes/k8s.io#677, but that should be sorted out by EOD tomorrow. The auditor has had fixes to child manifest detection and this has been rolled out earlier today. There is an internal Google change that will start rolling out on Wednesday (April 1) morning for the flip itself. As k8s-artifacts-prod has been a superset of google-containers for a while now, the transition should be seamless. (However, I will perform another backfill if necessary tomorrow). The backup stuff is in a bit of a pinch but I don't think it will take longer than tomorrow to sort out (in time for the flip on Wed morning). |
@listx -- Thanks for the update! I think we're fine for day 1 as long as the backfill is set (which it is) and we've got a go-forward plan for the backups (which we do). On my end, I've successfully tested the Releng changes here. I'm going to do a few spot-checks just in case, but we should be all good to go! :) |
The flip is in progress. Charts and updates haven been posted here: https://groups.google.com/d/msg/kubernetes-sig-release/ew-k9PEBckQ/mSa7KGeUCAAJ |
Forgot to update this thread, but TL;DR: the flip has been rolled back due to an unforeseen issue. Details here: https://groups.google.com/d/msg/kubernetes-sig-release/ew-k9PEBckQ/SZC2KeFYAwAJ We will attempt the flip again in the coming weeks; I will update this thread again once we decide on the date. |
Last I chatted w/ @listx ETA is in a few weeks. |
I gave a quick update at the WG meeting. TL;DR is that over time, bad
assumptions grow deep roots. We're disentangling the roots now, but it
reaches across several teams, and we've already caused one problem with
this, so "once bitten, twice shy" is in full effect. We believe we're
close. O(weeks) seems right.
…On Wed, May 13, 2020 at 8:12 PM Stephen Augustus ***@***.***> wrote:
Last I chatted w/ @listx <https://github.com/listx> ETA is in a few weeks.
They're still working on some stuff on the Google side.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#270 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABKWAVDEWRZ4DKMLMOMEW53RRNORLANCNFSM4DCOKK6A>
.
|
I vote to close this as VDF was completed on July 24, 2020. |
Google Infra --> K8s Infra tasks (ordered by priority):
k8s-artifacts-prod
GCR is a superset of google-containers (aka backfiling; this has already been done and is easy to check before VDF happens)<somewhere>
Release Engineering
k8s-staging-kubernetes
GCP project (prod staging project)k8s-staging-kubernetes
promoter-manifest to point to test prod namespacekubernetes-release-test
GCB write onk8s-staging-kubernetes
GCRk8s-staging-kubernetes
)Original note from @jbeda:
The text was updated successfully, but these errors were encountered: