Begin building/storing kube-cross images on K8s Infra #1133
Description
What would you like to be added:
Initial work
- (build: Enable kube-cross image-building on K8s Infra kubernetes#88562) k/k PR to enable kube-cross push/pull from K8s Infra GCR
- Add reviewers/approvers on build images
- Search/replace Google Infra kube-cross locations for K8s Infra
- Update kube-cross make targets
- Add a GCB (Google Cloud Build) config file (cloudbuild.yaml)
- (releng: Grant access to push images in build-image GCP project k8s.io#603) Add Release Engineering OWNERS to k8s.io:
- groups.yaml update
- k8s-infra-staging-build-image OWNERS
- (kube-cross: Backfill promotion of active k8s.gcr.io/kube-cross images k8s.io#608) Backfill and promotion of most recent kube-cross images (current kube-cross for each active release branch)
- Cherry-picks of build: Enable kube-cross image-building on K8s Infra kubernetes#88562
- (images: Update k8s-cloud-builder to use the new kube-cross location #1141) Update k8s-cloud-builder to use the new kube-cross location
RFC
- (images: Move kube-cross image building to k/release #1140) Move kube-cross image building to k/release
- (releng: Enable kube-cross image building/pushing test-infra#16494) k/test-infra PR to enable image pushing
Cleanup
- (Update to Golang 1.13.9 kubernetes#89275) Remove kube-cross building from k/k
Why is this needed:
One of the follow-up items in our quarterly golang update is to transition ownership of Golang bumps to the @kubernetes/release-engineering group. Part of the Golang bump is updating the kube-cross image, which today can only be done by a few Googlers (@BenTheElder, @javier-b-perez, @listx (maybe)).
/assign