Add CAPA v26.1.0

[nprokopic]

Towards giantswarm/roadmap#3610

This release updates the apps and components, keeping them up to date with the latest v25 release. It also brings improvements for the container registry usage.

Change details compared to CAPA 26.0.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.

cert-manager 3.7.9

Fix

• Remove quotes from acme-http01-solver-image argument. The quotes are used when looking up the image which causes an error.

Update

• Improves container security by setting runAsGroup and runAsUser greater than zero for all deployments.

containerlinux 3815.2.5

Changes since Stable 3815.2.4

Security fixes:

• openssh (CVE-2024-6387)

Updates:

• Linux (6.1.96)
• openssh (9.7_p1)

cilium 0.25.1

Changed

• Fix regression setting Policy BPF Max map policyMapMax back to 65536 from 16384.
• Upgrade cilium to v1.15.6.

Checklist

• Roadmap issue created
• Release uses latest stable Flatcar
• Release uses latest Kubernetes 1.26.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]

Debugging e2e tests

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

[nprokopic]

e2e tests have failed because the AMI does not exist. v26.1.0 changes Flatcar version, while keeping the same k8s version, but the new image does not exist as the previous one has been also built manually. Will trigger a new image-build for this.

[nprokopic]

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

[nprokopic]

Testing minor upgrade 26.0.0 to 26.1.0.

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

[nprokopic]

Upgrade tests have passed, but cluster deletion failed (I have created an issue for this already today giantswarm/roadmap#3618).

[nprokopic]

Testing major upgrade 25.0.0 to 26.0.0.

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

[tinkerers-ci]

releases-test-suites

Run name	pr-releases-1332-releases-test-suiteshpc6f
Commit SHA	857f50a
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]

@T-Kukawka @weatherhog @gawertm please check the announcement and README for v26.1.0. It mentions a new cluster-aws version with Zot changes, as well as other app/component changes that your teams own and we have already included in v25.1.0.

v26.1.0 has been tested and can be merged after this PR has been approved.