Skip to content
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

Tasks for Kubernetes 1.26 #7129

Closed
13 tasks
sbueringer opened this issue Aug 30, 2022 · 3 comments
Closed
13 tasks

Tasks for Kubernetes 1.26 #7129

sbueringer opened this issue Aug 30, 2022 · 3 comments
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@sbueringer
Copy link
Member

sbueringer commented Aug 30, 2022

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]
@sbueringer sbueringer changed the title Tasks for Kubernetes 1.25 Tasks for Kubernetes 1.26 Aug 30, 2022
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Aug 30, 2022
@sbueringer sbueringer added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Aug 30, 2022
@k8s-ci-robot k8s-ci-robot removed the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Aug 30, 2022
@ykakarap
Copy link
Contributor

/close
re-opening with new template.

@k8s-ci-robot
Copy link
Contributor

@ykakarap: Closing this issue.

In response to this:

/close
re-opening with new template.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@ykakarap
Copy link
Contributor

ykakarap commented Dec 7, 2022

New issue: #7671

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

3 participants