Update kubernetes to latest version
sayantani11 opened this issue · 9 comments
/kind feature
Describe the solution you'd like
As we know the last release version of Kubernetes happens to be 1.22, but the project is still set up based on version 1.20.9. So we need to update it in the files:
hack/ci/e2e-conformance.sh
scripts/ci-e2e.sh
export KUBERNETES_MAJOR_VERSION="1"
export KUBERNETES_MINOR_VERSION="22"
export KUBERNETES_PATCH_VERSION="0"/good-first-issue
/help
@sayantani11:
This request has been marked as suitable for new contributors.
Guidelines
Please ensure that the issue body includes answers to the following questions:
- Why are we solving this issue?
- To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
- Does this issue have zero to low barrier of entry?
- How can the assignee reach out to you for help?
For more details on the requirements of such an issue, please see here and ensure that they are met.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.
In response to this:
/good-first-issue
/help
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.
/assign
Looking out for a similar good first issue, thanks for posting!!
it is not only updating this the capg project. we also need to build those images
made a PR to update the images to the latest kubernetes-sigs/image-builder#733 and after that, we can check if the images are available and then update the jobs here and in the test-infra repo
@cpanato Can I make the PR in test-infra?
@sayantani11 sure, need to update the conformance test to match the k8s version that we will use https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes-sigs/cluster-api-provider-gcp/cluster-api-provider-gcp-presubmits.yaml#L193
but also need to wait for https://prow.k8s.io/?job=periodic-image-builder-gcp-all-nightly for the next run today to build the new images and then update the k8s version and image name in the PR above.
you can open the pr in test infra but we need to wait the images/update in capg PR
/close
@sayantani11: Closing this issue.
In response to this:
/close
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.