Add GitHub workflows for OS testing #3388
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Introduce a callable GitHub workflow that leverages the Terraform modules for OS testing to bring up a k0s cluster on AWS against which Kubernetes conformance tests will be executed. The workflow features parallel test execution to speed up test duration, if desired. Note that test results collected in parallel are most likely not accepted by the Kubernetes conformance test repo. If the tests should be submitted there, it's advised to set the `e2e-concurrency- level` to 1. Moreover, provide a matrix workflow that bundles up the first one into a matrix build, so that multiple OS and network provider configurations may be tested using a single workflow, and a nightly trigger which chooses a single OS/network provider combination to be run on a nightly basis. Signed-off-by: Tom Wieczorek <[email protected]>
twz123
force-pushed
the
k0s-ostests-workflows
branch
from
468fb91
to
52a1dcb
Compare
jnummelin
reviewed
Aug 16, 2023
| # combinations and select an entry based on the current day. This approach | ||
| # ensures that, if run once each day, there is a significant variation in | ||
| # parameter values each day while also guaranteeing that every combination | ||
| # will be chosen at some point. |
There was a problem hiding this comment.
Did I understand this correctly: We have 22 OSes and 2 network providers on the matrix, this means 44 items. So each combo, say Alpine 3.17 with Calico, will be tested every 44 days?
There was a problem hiding this comment.
Yes, that's the idea. Every day another OS and network provider until all permutations have been tested. Then start over from the beginning.
There was a problem hiding this comment.
Starting from today, this would be list of combinations for each day:
rocky_9/kuberouter
ubuntu_2204/calico
centos_9/kuberouter
debian_12/calico
oracle_9_1/kuberouter
rhel_9/calico
ubuntu_2304/kuberouter
alpine_3_17/calico
centos_7/kuberouter
debian_10/calico
fcos_38/kuberouter
fedora_38/calico
flatcar/kuberouter
oracle_7_9/calico
rhel_7/kuberouter
rocky_8/calico
ubuntu_2004/kuberouter
centos_8/calico
debian_11/kuberouter
oracle_8_7/calico
rhel_8/kuberouter
rocky_9/calico
ubuntu_2204/kuberouter
centos_9/calico
debian_12/kuberouter
oracle_9_1/calico
rhel_9/kuberouter
ubuntu_2304/calico
alpine_3_17/kuberouter
centos_7/calico
debian_10/kuberouter
fcos_38/calico
fedora_38/kuberouter
flatcar/calico
oracle_7_9/kuberouter
rhel_7/calico
rocky_8/kuberouter
ubuntu_2004/calico
centos_8/kuberouter
debian_11/calico
oracle_8_7/kuberouter
rhel_8/calico
There was a problem hiding this comment.
Specific combinations or bulk tests for many configurations may be triggered manually via the matrix job, if needed.
jnummelin
approved these changes
Aug 24, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Introduce a callable GitHub workflow that leverages the Terraform modules for OS testing to bring up a k0s cluster on AWS against which Kubernetes conformance tests will be executed.
The workflow features parallel test execution to speed up test duration, if desired. Note that test results collected in parallel are most likely not accepted by the Kubernetes conformance test repo. If the tests should be submitted there, it's advised to set the
e2e-concurrency-levelto 1.Moreover, provide a matrix workflow that bundles up the first one into a matrix build, so that multiple OS and network provider configurations may be tested using a single workflow, and a nightly trigger which chooses a single OS/network provider combination to be run on a nightly basis.
See:
Type of change
How Has This Been Tested?
Checklist: