New Kubernetes Release - IBM-Cloud/cloud-provider-ibm GitHub Wiki
The following steps are required to create a new branch for a new Kubernetes release:
-
Create new Label for the new release. "release-1.xx"
-
Create new branch for this new Kubernetes release
- Select the current branch from which the new branch will be created.
- In the
Find or create a branch...
field under theBranch
drop-down menu, enter the new branch namerelease-<major>.<minor>
where<major>.<minor>
is the Kubernetes major and minor version (e.g.release-1.34
)
-
Update dependabot.yml configuration
-
Update kube-update.yml Github Action workflow
-
go.mod
andgo.sum
dependencies are kept up to date with the dependabot. Dependabot will not generate the initial pull request to update thego.mod
from prior version of k8s modules to an "alpha" version. The initialgo.mod
update for the new release needs to be done manually.- Ensure you have correct version of GO installed on laptop
- Checkout the new release branch that just created
- Update
go.mod
:- Change each of the direct
k8s.io
modules to new release/patch level - Remove all indirect references to
k8s.io
modules that are using the old release
- Change each of the direct
- Run:
go mod tidy
- Check the
go.mod
that it contains the correct version of GO, if not then edit it manually and rerun:go mod tidy
- Create pull request
- Get the pull request reviewed and merged
-
The new branch needs to be made the "default" branch for the repository. This is done in the repo Settings under the
Branches
tab