Skip to content

Tasks for Kubernetes 1.26 #7129

@sbueringer

Description

@sbueringer

This issue is tracking the list of tasks that should be implemented when Kubernetes v1.26 is released.
Currently, we are waiting for the Kubernetes release and we will for a few months, mostly opening this already for tracking purposes

For prior art please see #6661

  • CI:

    • CAPD:
      • docker.yaml: KUBERNETES_ env vars in variables
      • kind_provider.go, docker/*, ... (just grep for the previously used version in CAPD)
    • Jobs:
      • Add new periodic upgrade jobs, for all release where we want to support the new Kubernetes version
      • Adjust presubmit jobs so that we have the latest upgrade jobs available on PRs (for all releases)
      • Update INIT_WITH_KUBERNETES_VERSION
  • Book:

  • Release specific issues:

  • After a Kubernetes release is cut a controller-runtime version is created. When the CR version is available we have to:

    • Bump controller-runtime to use new Kubernetes Go libraries (controller-runtime, controller-tools, client-go, ...)
      • This can include upgrading the Go version (we're using the same as k/k)
    • Update KUBEBUILDER_ENVTEST_KUBERNETES_VERSION in Makefile
    • Bump conversion-gen in Makefile via CONVERSION_GEN_VER
    • If the new Kubernetes version uses a new Go version
      • Jobs: Update kubekins-e2e images used for jobs running against main
        • Potentially it makes sense to switch to the latest ("master") version of kubekins-e2e if there is no -{KUBERNETES-VERSION} tag of the image already.
      • Update go version:
        • .github/workflows
        • .golangci.yml (+ corresponding workflow file)
        • cloudbuild YAMLs (to use an image with the current go version)
        • hack/ensure-go.sh
        • netlify.toml
        • Makefiles
        • Tiltfile
        • [opt] go.mod files (only if we want to increase the minimum supported version of consumers) [DOES NOT APPLY]

Metadata

Metadata

Assignees

No one assigned

    Labels

    lifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions