-
Notifications
You must be signed in to change notification settings - Fork 442
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
Integrate krel obs
into the release process
#1248
Comments
I can help with this. I'll add this issue to our project board so that we properly follow it. |
Shouldn't this be in kubernetes-release, rather than cri-tools ? |
The automation will happen in this repository, we can also consider moving the specfile here. |
@kubernetes-sigs/release-engineering how about:
|
@saschagrunert I think this is a solid plan. I would only try to avoid having a new repo for packaging (because getting repos in k or k-sigs is a more complicated process and it's not scalable). |
@xmudrii I'd like to try a full automation here, means we would require a service account being able to push to https://console.cloud.google.com/storage/browser/k8s-artifacts-cri-tools. Can we create on in kubernetes/k8s.io? |
@saschagrunert Yes, please create an issue in k/k8s.io to track getting a new service account. |
@xmudrii closing the loop: kubernetes/k8s.io#5957 |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
We still need this, and could also think about proposing an automated vendor PR for the RC of a new Kubernetes version. This could include a hint that we may want to cut a release afterwards. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
@xmudrii do you plan to work in this before v1.31 get's released? |
@saschagrunert Yes, I'll be looking into this issue this week. |
Let me know if you need anything, would be awesome to deliver it this cycle. |
@xmudrii I'm planning to release cri-tools v1.31 this week. Do we still want to invest in automation or plan that for 1.32? |
First of all we have to publish the release artifacts to the Google Cloud Bucket:
Publishes the GitHub artifacts in https://console.cloud.google.com/storage/browser/k8s-artifacts-cri-tools/release
Then we need to run the following commands to release cri-tools in OBS:
Runs a Google Cloud Build job and stages:
https://build.opensuse.org/package/show/isv:kubernetes:core:stable:v1.28:build/cri-tools
Runs a Google Cloud Build job and releases:
https://build.opensuse.org/package/show/isv:kubernetes:core:stable:v1.28/cri-tools.20230814075509
Goal is to integrate the steps above into our release workflow, containing the right amount of permissions:
https://github.com/kubernetes-sigs/cri-tools/blob/master/.github/workflows/release.yml
@kubernetes-sigs/release-engineering we need:
krel obs
k8s-artifacts-cri-tools
The text was updated successfully, but these errors were encountered: