Closed christopherhein closed 3 years ago
/milestone v0.1.x
@vincepri do you have any examples or guides in how other Cluster API Providers handle releases and what we need to setup? I believe we already have a lot of the tooling in-place but just need to wire it all together.
For releases, we usually have a bunch of things setup:
The above was built on top of what the default Makefile was at the time we built the CAPI project with kubebuilder. If you need some sync time happy to jump on Zoom and chat about the steps.
There are also some bits to configure in test-infra
, and in the k/k8s.io
repositories.
@vincepri for the Cloudbuild job, do we need to make our own gcloud project or is this picked up from prow? I guess maybe that is setup here - https://github.com/kubernetes/test-infra/blob/master/config/jobs/image-pushing/k8s-staging-cluster-api.yaml ?
/assign
@christopherhein Yes the setup is there, you'll also need to request a GCP project like the one in here https://github.com/kubernetes/k8s.io/tree/main/audit/projects/k8s-staging-cluster-api
Awesome, thanks that part is what I was missing!
I forgot I cleaned up the Makefile
in the last PR adding Prow presubmits - https://github.com/kubernetes-sigs/cluster-api-provider-nested/blob/main/Makefile#L300-L351
/close
@christopherhein: Closing this issue.
This was completed across many PRs and testing.
Prior to the first version being released we need to add to the
scripts/
dir the proper release scripts as well as setup Prow release jobs. For now we should have just CAPN covered, we'll eventually create separate jobs for virtualcluster releases.TODOS:
Makefile
prow
jobs