-
Notifications
You must be signed in to change notification settings - Fork 178
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
Use K8s v1.29.0 in e2e test #828
Conversation
/ok-to-test |
/test pull-cloud-provider-vsphere-e2e-test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
generally lgtm, some minor questions.
/lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could propably also cleanup the variables part, but I think its okay to keep it comparable.
I think with the changes suggested this should be a good step to test with latest stable CAPI & CAPV releases and Kubernetes 1.29.0. I think it would be good if we talk ~ 1 month before the Kubernetes 1.30 release to see if we want to start bumping towards 1.30 (at this point we should also already know with CAPI & CAPV versions are needed to create 1.30 clusters). |
Something worth highlighting. The Example:
=> Given that, I would recommend to get rid of the controller-runtime dependency in the top-level go.mod file (cc @DanielXiao @lubronzhan) |
Pretest Job pull-cloud-provider-vsphere-e2e-test runs against K8s v1.23.5 Clusters which are already out of support in Cluster-API. This patch bumps dependent CAPI to 1.6.1 and CAPV to 1.9.0 to deploy v1.29.0 Clusters. It also adds a makefile target to run test locally with any development images manually pushed to a registry. This is helpful for local development because you don't have to create a PR for pushing the image to gcr.io/cloud-provider-vsphere/cpi/pr/manager. This patch also remove variable INIT_WITH_KUBERNETES_VERSION. KUBERNETES_VERSION will be used for both bootstrap and workload cluster version.
f5c8abc
to
65b9757
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The PR looks great, just one minor question
/lgtm
new: "imagePullPolicy: IfNotPresent" | ||
files: | ||
- sourcePath: "../data/shared/metadata.yaml" | ||
- name: cluster-api |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one minor question @DanielXiao :
Will it have any side effects if we only support v1beta1, is it safe to remove the v1alpha3 and v1alpha4 support?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are only installing one version of Cluster API which is v1.6.1. Dropping v1.5, v1.4, ... doesn't change anything.
The apiVersions supported will be the one supported by Cluster API v1.6.1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some additional context. In core CAPI and in CAPV we have tests that test the following:
- install old versions of CAPI & CAPV
- create a workload cluster
- upgrade to newer versions of CAPI & CAPV
- modify the workload cluster
The idea is to verify if we can upgrade from a set of CAPI & CAPV versions to another one. This is the reason why we have to define multiple CAPI & CAPV versions in this config file.
Here in CPI you only want to create a workload cluster with specific versions of CAPI & CAPV. There is no upgrade test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gotcha, thanks @sbueringer !
Thx! /lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: DanielXiao, XudongLiuHarold The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/cherry-pick release-1.29 |
@DanielXiao: new pull request created: #839 In response to this:
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. |
What this PR does / why we need it:
Pretest Job pull-cloud-provider-vsphere-e2e-test runs against K8s v1.23.5 Clusters which is already out of support in Cluster-API.
This patch bumps dependent CAPI to 1.6.1 and CAPV to 1.9.0 to deploy v1.29.0 Clusters. It also adds a makefile target to run test locally with any development images manually pushed to a registry. This is helpful for local development because you don't have to create a PR for pushing the image to gcr.io/cloud-provider-vsphere/cpi/pr/manager.
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #780Special notes for your reviewer:
Release note: