-
Notifications
You must be signed in to change notification settings - Fork 32
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
[TEST] [Release Testing] Test installed CRD API versions of system charts #1314
Comments
m-ildefons
added a commit
to m-ildefons/harvester-tests
that referenced
this issue
Jun 10, 2024
Add test which checks if the CRD versions defined in the cluster match the versions in the subcharts in the git repo. This test ensures that the subcharts in the release version don't unexpectedly change their API versions within a minor Harvester release. To implement this test, additional infrastructure for the Kubernetes API has been added. fixes: harvester#1314 Signed-off-by: Moritz Röhrich <moritz.rohrich@suse.com>
m-ildefons
added a commit
to m-ildefons/harvester-tests
that referenced
this issue
Jun 10, 2024
Add test which checks if the CRD versions defined in the cluster match the versions in the subcharts in the git repo. This test ensures that the subcharts in the release version don't unexpectedly change their API versions within a minor Harvester release. To implement this test, additional infrastructure for the Kubernetes API has been added. fixes: harvester#1314 Signed-off-by: Moritz Röhrich <moritz.rohrich@suse.com>
m-ildefons
added a commit
to m-ildefons/harvester-tests
that referenced
this issue
Jun 10, 2024
Add test which checks if the CRD versions defined in the cluster match the versions in the subcharts in the git repo. This test ensures that the subcharts in the release version don't unexpectedly change their API versions within a minor Harvester release. To implement this test, additional infrastructure for the Kubernetes API has been added. fixes: harvester#1314 Signed-off-by: Moritz Röhrich <moritz.rohrich@suse.com>
m-ildefons
added a commit
to m-ildefons/harvester-tests
that referenced
this issue
Jun 10, 2024
Add test which checks if the CRD versions defined in the cluster match the versions in the subcharts in the git repo. This test ensures that the subcharts in the release version don't unexpectedly change their API versions within a minor Harvester release. To implement this test, additional infrastructure for the Kubernetes API has been added. fixes: harvester#1314 Signed-off-by: Moritz Röhrich <moritz.rohrich@suse.com>
m-ildefons
added a commit
to m-ildefons/harvester-tests
that referenced
this issue
Jun 10, 2024
Add test which checks if the CRD versions defined in the cluster match the versions in the subcharts in the git repo. This test ensures that the subcharts in the release version don't unexpectedly change their API versions within a minor Harvester release. To implement this test, additional infrastructure for the Kubernetes API has been added. fixes: harvester#1314 Signed-off-by: Moritz Röhrich <moritz.rohrich@suse.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What's the test to develop? Please describe
To make release testing easier develop tests that cross-check CRD API versions of the Harvester release (as it is installed on the system under test) against the repository contents
Describe the items of the test development (DoD, definition of done) you'd like
Definition of Done:
The test under point 2 of this upgrade test run should be covered: #1254 (comment)
Stretch Goal:
The tests under point 1 of the above upgrade test run should be covered.
While this stretch goal doesn't cover CRD API versions, it should be fairly simple to implement once the other goal is done, since most of the needed fixtures are already included in the other goal.
Additional context
https://confluence.suse.com/display/HARV/Release+Testing+HowTo
The text was updated successfully, but these errors were encountered: