New Kubernetes Release

The following steps are required to create a new branch for a new Kubernetes release:

1. Create new Label for the new release. "release-1.xx"

2. 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 the Branch drop-down menu, enter the new branch name release-<major>.<minor> where <major>.<minor> is the Kubernetes major and minor version (e.g. release-1.35)

3. Update dependabot.yml configuration

4. Update kube-update.yml Github Action workflow

5. Update golangci-update.yml Github Action workflow

6. Determine the version of latest Kubernetes Releases

7. Click on that release to get to github source code. Located the go.mod to determine the the GO version

8. Update the go.mod / go.sum with the information retrieved in the previous two steps

   • Install the same version of GO that is being used for this Kubernetes release
   • Checkout the new release branch that was just created
   • Update go.mod:
     • Change each of the direct k8s.io modules to new release/patch level (such as v0.35.0-alpha.1)
       • NOTE: The GO libraries are v0. where as the Kubernetes release is v1.
     • Remove all indirect references to k8s.io modules that are using the old release
     • Update the GO version
   • Run: go mod tidy

9. Run a local build of the repo: make all. Fix each error until the the new branch compiles cleanly.

10. Check in / merge the new branch

11. Make sure the Github actions build the branch cleanly

12. Set the new branch to be the "default" branch. This is done in the repo Settings under the General tab

13. Delete files no longer needed in the previous "default" branch

    • .github/workflows/dispatch-pr-create.yml
    • .github/workflows/golangci-update.yml
    • .github/workflows/kube-update.yml
    • .github/dependabot.yml

14. Update the Kubernetes-to-OpenShift-releases with the new release

15. Within 24 hours, the kube-update.yml Github Action workflow will run and update the remaining files in the new branch to the new Kubernetes release