-
Notifications
You must be signed in to change notification settings - Fork 192
Conversation
Cluster Generation A/B Results: |
f598f35
to
87c3681
Compare
Cluster Generation A/B Results: |
87c3681
to
99bb7df
Compare
Cluster Generation A/B Results: |
99bb7df
to
28d78f4
Compare
Cluster Generation A/B Results: |
28d78f4
to
46b1a9c
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.
work in progress. Functionality is there but needs refactoring where possible to avoid code clutter
Cluster Generation A/B Results: |
Thanks for the PR. Changes look good, but I'm not sure if it would be feasible for automation to have two TKRs with slightly different versions of packages and check the package version is actually bumped after the upgraded. |
Hi @adduarte, thanks for the change! Currently TKGS E2E tests are not consuming |
I assume generic infrastructure-agnostic tests are still fine (and maybe even better) to be added to the e2e common. |
Yeah that makes sense if the testing also works for AWS. But for TKGS test, we still need to add entry in tkgs folder for these tests to be triggered as well when we run TKGS tests. Because currently we trigger TKGS E2E tests by
In the long term I agree with @maralavi that it would better if shared logic can be reused by different kind of tests.. I find it somewhat confusing too as TKGS tests are running individually. |
Hi @adduarte, actually maybe we could continue to put the upgrade testing code in the shared package, and just add an entry in TKGS testing folder to trigger the upgrade testing. @ggpaue's PR(#2943) does in that way. That might be much easier since the testing code might need to access to some variables or structs defined in the shared package. |
yes. that is bigger problem than just this pr :( We have been adding all our automation to e2ecommon. I think @HL-EverGreen is correct. I think is best if we add a call to E2CommonSpecInput to the tkgs_workload_cluster_test.go |
46b1a9c
to
dcfb314
Compare
Cluster Generation A/B Results: |
Latest version of patch makes it so that everything is defined in the shared package, and the tkgs tests just make a call to it. |
Codecov Report
@@ Coverage Diff @@
## main #3018 +/- ##
==========================================
- Coverage 44.22% 44.11% -0.11%
==========================================
Files 417 416 -1
Lines 42304 42225 -79
==========================================
- Hits 18707 18629 -78
+ Misses 21882 21878 -4
- Partials 1715 1718 +3
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
dcfb314
to
a848e05
Compare
53b9b99
to
3e0ce43
Compare
continue | ||
} | ||
|
||
specVersionIsNewer, err := isNewerVMwareVersion(tkrs[i].Spec.Version, currentTkrVersion) |
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.
if the spec version (from the tkr we are looking at) is newer (and compatible) we compare it to any version we already found, to pick the older of the two. This will ensure we pick the next avaiable version: (newer than our currentVersion, but the older tan all other newer )
3e0ce43
to
51558ad
Compare
Cluster Generation A/B Results: |
Cluster Generation A/B Results: |
Cluster Generation A/B Results: |
700c954
to
c7dc4ab
Compare
Cluster Generation A/B Results: |
Cluster Generation A/B Results: |
c7dc4ab
to
346adf6
Compare
Cluster Generation A/B Results: |
Tested the following locally:
used command:
results:
|
346adf6
to
538efb7
Compare
Cluster Generation A/B Results: |
538efb7
to
e3f12ba
Compare
Cluster Generation A/B Results: |
e3f12ba
to
3da9c48
Compare
adds the required code to execute an upgrade test on a class based cluster
3da9c48
to
6c143ce
Compare
Cluster Generation A/B Results: |
Cluster Generation A/B Results: |
cc_cluster lifecycle upgrade test - upgrade
What this PR does / why we need it
Adds logic to verify class cluster upgrade for integration tests.
Which issue(s) this PR fixes
Fixes #2450
Describe testing done for PR
Release note
Additional information
Special notes for your reviewer
Tested the following locally:
used command:
results: