This repository contains workload cluster release notes and changelogs.
Workload cluster releases can be in
different states, namely active, deprecated and wip. With pull requests
merged to the master branch, workload cluster releases get automatically deployed
to all Giant Swarm installations.
-
v29
-
v28
-
v27
-
v26
-
v25
-
v20
-
v19
-
v18
-
v17
-
v16
-
v15
-
v14
-
v13
-
v12
-
v11
-
v10
-
v9
-
v8
-
v29
-
v28
- v28.0
-
v27
- v27.0
-
v26
- v26.0
-
v25
- v25.0
-
v20
- v20.0
-
v19
-
v18
-
v17
-
v17.2
-
v17.1
-
v17.0
-
-
v16
-
v15
- v15.1
- v15.0
-
v14
-
v13
-
v12
-
v11
-
v9
- v9.0
-
v8
-
v16
-
v15
-
v14
-
v13
-
v12
-
v11
-
v9
-
v8
- v27
- v27.0
To trigger the Workload Cluster End-to-End tests for each new Release added in a PR, add a comment with the following:
/run releases-test-suites
This will automatically trigger tests for all new releases detected in the PR and will run them against the appropriate standard and upgrade test suites for the provider.
If you need to run tests for a specific Release (from the PR) or a different test suite, you can do so with the two following, optional parameters:
TARGET_SUITES- a comma separated list of test suites to trigger (e.g../providers/capa/standard)TARGET_RELEASES- a comma separates list of Releases to trigger from the PR (e.g.aws-25.0.0-example.1)
The upgrade tests will first install a cluster using the latest previously published release and then upgrade to using the release found in the PR. If you need to override the starting Release version (to test upgrading from an earlier release) you can do so by setting the PREVIOUS_RELEASE parameter on the trigger comment (e.g. /run releases-test-suites PREVIOUS_RELEASE=28.1.0)
The workload cluster E2E tests are enforced by our PR gatekeeper to ensure they are passing before PRs are allowed to be merged.
To trigger the CNCF Conformance tests for a new Release added in a PR, add a comment with something similar to the following:
/run conformance-tests PROVIDER=capa RELEASE_VERSION=29.1.0
The following parameters are required:
PROVIDER- the name of the provider the release is forRELEASE_VERSION- the version of the Release to test from the PR
Please note that these tests take roughly 2 hours to run, so best to only run once all other changes are ready.
Currently the conformance tests can only run against a single Release. If you have more than one Release to test in your PR you can comment multiple times with the parameters changed, but be aware that only a single GitHub check will be added to the PR so you will need to manually confirm each has passed in Tekton.
Currently the conformance tests are not enforced by our PR gatekeeper.