cluster-api-provider-vsphere
cluster-api-provider-vsphere copied to clipboard
kubernetes-sigs
Explore k8s image promoter to k8s.gcr.io
/kind feature
Describe the solution you'd like At the last subproject meeting for CAPV, it was discussed that we want to look more into the k8s image promoter.
The idea here is that we file PRs to https://github.com/kubernetes/k8s.io/tree/master/k8s.gcr.io when we want to have an image promoted to the k8s gcr.io namespace (which conveniently has us, eu, and asia domains).
The promoter process is intended to be used with the image promoter staging repos, but it doesn't actually have to be according to @dims. What this means is that we should be able to promote our GA releases straight from gcr.io/cluster-api-provider-vsphere/release/manager if we want to. Looking at the existing promotion configs, we would be the first to do it this way, but I think our existing build/publish infrastructure is quite streamlined and is not necessarily something we want to abandon.
But this issue is for discussion around that.
/cc @andrewsykim /cc @akutz /cc @dims
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta. /lifecycle stale
@randomvariable @yastij This could be something that we can incorporate in the release automation process. wdyt?
@sbueringer: Closing this issue.
In response to this:
/close
This will be part of #2051
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.
