CAPV: Release v28.0.0.

[njuettner]

Towards: giantswarm/roadmap#3716

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.

[tityosbot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[tinkerers-ci]

Note

As this is a draft PR no triggers from the PR body will be handled.

If you'd like to trigger them while draft please add them as a PR comment.

[njuettner]

/run releases-test-suites

[tinkerers-ci]

releases-test-suites

Run name	pr-releases-1457-releases-test-suitesn76nw
Commit SHA	1d5c65c
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

[njuettner]

/run releases-test-suites TARGET_SUITES=./providers/vsphere/upgrade

[tinkerers-ci]

releases-test-suites

Run name	pr-releases-1457-releases-test-suites86pjx
Commit SHA	1d5c65c
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

[njuettner]

/run releases-test-suites TARGET_SUITES=./providers/vsphere/upgrade TARGET_RELEASES=vsphere-28.0.0

[tinkerers-ci]

releases-test-suites

Run name	pr-releases-1457-releases-test-suitesxnn7x
Commit SHA	1d5c65c
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

[njuettner]

/run releases-test-suites

[tinkerers-ci]

releases-test-suites

Run name	pr-releases-1457-releases-test-suitesk7mmk
Commit SHA	1d5c65c
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

[njuettner]

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

[tinkerers-ci]

releases-test-suites

Run name	pr-releases-1457-releases-test-suites8xzwp
Commit SHA	1d5c65c
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

[njuettner]

/run releases-test-suites

[tinkerers-ci]

releases-test-suites

Run name	pr-releases-1457-releases-test-suitesblv2j
Commit SHA	1d5c65c
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]

Apart from my comment, I assume we only added the apps of the cluster-vsphere chart and kept the versions and dependencies as they are currently defined there, right?

[Gacko]

Also maybe consider re-generating the releases.json by running go run renovate.go upfront. 🙂 This spares the follow-up commit by CI.

[njuettner]

/run releases-test-suites

[tinkerers-ci]

releases-test-suites

Run name	pr-releases-1457-releases-test-suites2nxrt
Commit SHA	eddd4fc
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