-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
🌱 E2E test to upgrade workload cluster #4130
🌱 E2E test to upgrade workload cluster #4130
Conversation
/hold WIP |
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.
thanks for the PR, added some quick comments on styling / wording.
/test pull-cluster-api-e2e-full-main |
700c7c6
to
6d949b7
Compare
/test pull-cluster-api-e2e-full-main |
cc @fabriziopandini PTAL, working on a prow job to run this with different combinations of versions. |
/assign @fabriziopandini |
test/e2e/cluster_upgrade_test.go
Outdated
. "github.com/onsi/ginkgo" | ||
) | ||
|
||
var _ = Describe("When upgrading a workload cluster and testing K8S conformance [K8SVersion-Upgrade]", func() { |
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.
I would suggest to document labels ([K8SVersion-Upgrade]
) in https://cluster-api.sigs.k8s.io/developer/testing.html#running-the-end-to-end-tests and cross link the list of labels in https://cluster-api.sigs.k8s.io/developer/e2e.html
Also, are you planning to sunset the [Periodic-K8SVersion] label?
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.
PTAL
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.
I'm a +1 on @fabriziopandini's suggestions regarding documenting the test labels and perhaps reusing [Periodic-K8SVersion]
if it follows the intent.
@srm09 Is there a reason we still have the /hold
on this?
.../data/infrastructure-docker/v1alpha4/cluster-template-md-and-machine-pool/kustomization.yaml
Outdated
Show resolved
Hide resolved
/unhold |
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.
I'm assuming there's a corresponding test-infra PR that updates our CI config so that tests are run without disruption. If there is one, can we link it here 🙂
d104154
to
ce5715e
Compare
cde84d2
to
6a2854c
Compare
/lgtm |
/test pull-cluster-api-e2e-full-main |
/test pull-cluster-api-test-main |
/retest |
176ca24
to
9344d40
Compare
/test pull-cluster-api-e2e-full-main |
@fabriziopandini Am unsure as to why this is failing. I have had a clean re-run for this locally multiple times. |
9344d40
to
43d46f5
Compare
/retest |
/test pull-cluster-api-verify |
@srm09 given the type of error in make verify my assumption is that you are using an older version of go locally. |
43d46f5
to
ef5fed9
Compare
/milestone v0.4.0 |
ef5fed9
to
08b3b8b
Compare
/test pull-cluster-api-e2e-full-main |
/lgtm |
@fabriziopandini Done |
This patch adds an E2E test to create a workload cluster containing of machinedeployment and machinepool. This cluster is then upgraded to another k8s version, including the CP, machine pool and machine deployment. To verify the status of the upgrade, conformance tests are run on the cluster post upgrade. This also updates the e2e run target to include an additional parameter named GINKGO_SKIP which can be used to skip ginkgo tests matching the regexp. Signed-off-by: Sagar Muchhal <[email protected]> Co-authored-by: Cecile Robert-Michon <[email protected]> Co-authored-by: Lubomir I. Ivanov <[email protected]> Co-authored-by: Fabrizio Pandini <[email protected]>
08b3b8b
to
3f7430d
Compare
@srm09: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
/test pull-cluster-api-test-main |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fabriziopandini 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 |
What this PR does / why we need it:
Adds a new E2E test to upgrade a workload cluster and run conformance tests to verify the upgrade
Which issue(s) this PR fixes:
Fixes #4043