-
Notifications
You must be signed in to change notification settings - Fork 26
MIgrate build and promotion of images from Kubebuilder GCP #60
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
Comments
Following some important info to help out on this one
Something like:
|
@camilamacedo86 I am interested in working on this task. |
It seems out of the scope but we probably need add more people in : https://github.com/kubernetes/k8s.io/pull/4586/files#r1682542243 (Just adding here for now) |
Thank you a lot for your terrfic work and help us understand how would be the process moving forward. Therefore, due the fact of this image only check the PR title it seems that make no sense we need to have the infrastructure for each and have a process where we need to build image in stage and then publish for prod. It seems that we can create a shell script or let people use the same implementation in other ways. So, lets close this one @sbueringer ^ +1 for your thought that the work is not valid here. |
Sounds reasonable to me |
We are using the project to generate the image gcr.io/kubebuilder/pr-verifier:$TAG_NAME. This image, generated by the project https://github.com/kubernetes-sigs/kubebuilder-release-tools, is used in the CI to verify PR emojis for release notes.
The goal of this one is move forward and use he regular image promotion / k8s infra to promote those images.
Be aware that the current images will be unavailable from March 18, 2025.
Motivation: kubernetes/k8s.io#2647 and kubernetes-sigs/kubebuilder#3907
The text was updated successfully, but these errors were encountered: