Add CAPA v25.2.0

[nprokopic]

Towards giantswarm/roadmap#3610

This release updates cluster-aws Helm chart, which brings improvements for container registry usage.

Change details compared to CAPA 25.1.0

cluster-aws 1.3.0

Changed

• All workload clusters will by default use Zot registry as a pull-through cache of Azure Container Registry.

Checklist

• Roadmap issue created
• Release uses latest stable Flatcar
• Release uses latest Kubernetes 1.25.x 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 RELEASE_VERSION=v28.0.0 PROVIDER=capa

For more details see the README.md

[nprokopic]

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

[nprokopic]

/run releases-test-suites TARGET_SUITES=./providers/capa/upgrade PREVIOUS_RELEASE=aws-v25.0.0

[nprokopic]

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

[nprokopic]

All upgrade tests have passed, it's the AfterSuite clean-up that failed

{"level":"info","ts":"2024-07-30T11:56:22Z","msg":"Checking if Cluster 't-tjupwewq9lhluvusov' still exists"}
  {"level":"info","ts":"2024-07-30T11:56:22Z","msg":"Still exists: Cluster 't-tjupwewq9lhluvusov' (finalizers: [cluster.cluster.x-k8s.io](http://cluster.cluster.x-k8s.io/))"}
  {"level":"info","ts":"2024-07-30T11:56:32Z","msg":"Checking if Cluster 't-tjupwewq9lhluvusov' still exists"}
  {"level":"info","ts":"2024-07-30T11:56:32Z","msg":"Still exists: Cluster 't-tjupwewq9lhluvusov' (finalizers: [cluster.cluster.x-k8s.io](http://cluster.cluster.x-k8s.io/))"}
  [FAILED] in [AfterSuite] - /app/internal/suite/setup.go:56 @ 07/30/24 11:56:42.456
[AfterSuite] [FAILED] [1808.051 seconds]
[AfterSuite] 
/app/internal/suite/setup.go:46

  [FAILED] Expected success, but got an error:
      <context.deadlineExceededError>: 
      context deadline exceeded
      {}
  In [AfterSuite] at: /app/internal/suite/setup.go:56 @ 07/30/24 11:56:42.456

I have created an issue for this giantswarm/roadmap#3618.

[nprokopic]

Testing minor upgrade 25.1.0 to 25.2.0

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

[tinkerers-ci]

releases-test-suites

Run name	pr-releases-1331-releases-test-suiteslnhxn
Commit SHA	5668b4e
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

[nprokopic]

Both standard and upgrade e2e tests suites have passed successfully ✔️ 🎉

• ✅ CAPA Standard suite - create v25.2.0 cluster
• ✅ CAPA upgrade suite - upgrade cluster from v25.0.0 to v25.2.0
  • ⚠️ AfterSuite (cluster deletion) failed due to irsa-operator bug. This is an MC component and the failure is unrelated to workload cluster releases. I have created an issue for this.
• ✅ CAPA upgrade suite - upgrade cluster from v25.1.0 to v25.2.0

IMO the e2e test results are good and we can merge this.

@giantswarm/sig-product please check the v25.2.0 announcement and README.

[nprokopic]

@T-Kukawka @weatherhog please check the announcement and README for v25.2.0. It mentions a new cluster-aws version with Zot changes.

v25.2.0 has been fully tested, it can be merged after being approved.

[nprokopic]

Thanks Tobi!