CAPA: Release v25.1.3.

[AndiDog]

Towards https://github.com/giantswarm/giantswarm/issues/31843

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 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]

@giantswarm/team-tenet do you want to bump cert-exporter?

[AndiDog]

/run releases-test-suites

[Gacko]

@giantswarm/team-tenet do you want to bump cert-exporter?

Yep, will do so.

[AndiDog]

/run releases-test-suites

[Gacko]

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

It doesn't really make sense to test the upgrade here as this is the first version after Vintage, right?

[AndiDog]

I still need to fix the aws-node-termination-handler behavior so it reacts to dying spot instances

[AndiDog]

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

[tinkerers-ci]

releases-test-suites

Run name	pr-releases-1516-releases-test-suitesz2z44
Commit SHA	abda4d5
Result	Failed ❌

📋 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

[AndiDog]

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

[tinkerers-ci]

releases-test-suites

Run name	pr-releases-1516-releases-test-suiteschdhq
Commit SHA	abda4d5
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

[AndiDog]

/run releases-test-suites

[AndiDog]

Forgot to set the base release for the test

/run releases-test-suites PREVIOUS_RELEASE=25.1.2 TARGET_SUITES=./providers/capa/upgrade

[tinkerers-ci]

releases-test-suites

Run name	pr-releases-1516-releases-test-suites8j24l
Commit SHA	2ce8cb5
Result	Failed ❌

📋 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

[tinkerers-ci]

releases-test-suites

Run name	pr-releases-1516-releases-test-suites6rm24
Commit SHA	2ce8cb5
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