CAPZ: Release v29.4.0.

[Gacko]

Checklist

• Roadmap issue created
• Release uses latest stable Flatcar
• Release uses latest Kubernetes patch version

Triggering E2E tests

To trigger the E2E test for each new Release added in this PR, add a comment with the following:

/run releases-test-suites

If your release is a new patch release for an older major release, you need to specify the previous release for use in upgrade tests, for example for 25.1.2 (exists) to 25.1.3 (added in your PR):

/run releases-test-suites PREVIOUS_RELEASE=25.1.2

If your release is a new minor release for an older major release, e.g. 25.3.0 (exists) to 25.4.0 (added in your PR), it works the same way:

/run releases-test-suites PREVIOUS_RELEASE=25.3.0

You can also limit which tests are run:

/run releases-test-suites TARGET_SUITES=./providers/capa/standard

If you want to trigger conformance tests, you can do so by adding a comment similar to the following:

/run conformance-tests PROVIDER=capa RELEASE_VERSION=29.1.0

For more details see the README.md.

[AndiDog]

I'll push our cluster-aws/aws-node-termination-handler stuff here since I need a commit in order to set E2E_RELEASE_VERSION/E2E_RELEASE_COMMIT in tests. Blocking the release until we've successfully tested the feature ;)

[AndiDog]

Oops, confused this one with a CAPA release

[Gacko]

I'll come up with CAPA tomorrow.

[Gacko]

/run releases-test-suites PREVIOUS_RELEASE=29.3.0

[tinkerers-ci]

releases-test-suites

Run name	pr-releases-1522-releases-test-suitesmhvhq
Commit SHA	e7ba39c
Result	Succeeded ✅

📋 View full results in Tekton Dashboard

Rerun trigger:
/run releases-test-suites

---

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run releases-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

Alternatively, or in addition to, you can also specify TARGET_RELEASES to trigger tests for specific releases. E.g. /run releases-test-suites TARGET_SUITES=./providers/capa/standard TARGET_RELEASES=aws-25.0.0-test.1

[Gacko]

/run releases-test-suites PREVIOUS_RELEASE=29.3.0

[tinkerers-ci]

releases-test-suites

Run name	pr-releases-1522-releases-test-suitesxxj9c
Commit SHA	7681cf0
Result	Succeeded ✅

📋 View full results in Tekton Dashboard

Rerun trigger:
/run releases-test-suites

---

Tip

To only re-run the failed test suites you can provide a TARGET_SUITES parameter with your trigger that points to the directory path of the test suites to run, e.g. /run releases-test-suites TARGET_SUITES=./providers/capa/standard to re-run the CAPA standard test suite. This supports multiple test suites with each path separated by a comma.

Alternatively, or in addition to, you can also specify TARGET_RELEASES to trigger tests for specific releases. E.g. /run releases-test-suites TARGET_SUITES=./providers/capa/standard TARGET_RELEASES=aws-25.0.0-test.1

[Gacko]

I'm skipping CI as I had to rebase this branch on top of master and don't want to run tests again just for this.