Release v20.1.4

[tuladhar]

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

This release upgrades cert-manager from v3.7.7 to v3.7.9:

• v3.7.9: Fixes an issue with quotes in cert-manager acme-http01-solver-image argument.
• v3.7.8: Improves container security by setting runAsGroup and runAsUser greater than zero for all deployments.

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

For more details see the README.md

Manual tests

• Upgrade works from v20.1.2 to v20.1.4
• Upgrade works from v20.1.3 to v20.1.4

[tuladhar]

/run releases-test-suites

[tuladhar]

/test e2e region=default flavour=default

[tuladhar]

/run releases-test-suites

[tinkerers-ci]

releases-test-suites

Run name	pr-releases-1308-releases-test-suitesczc45
Commit SHA	633957a
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

[tuladhar]

/run releases-test-suites

[tinkerers-ci]

releases-test-suites

Run name	pr-releases-1308-releases-test-suitestrkqf
Commit SHA	633957a
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

[tityosbot]

@T-Kukawka: The /test command needs one or more targets.
The following commands are available to trigger jobs:

• /test cis
• /test cncf region=default flavour=default
• /test cncf region=default flavour=eni
• /test e2e region=default flavour=default
• /test e2e region=china flavour=default
• /test e2e region=default flavour=eni
• /test upgrade region=default flavour=default
• /test upgrade region=china flavour=default
• /test upgrade region=default flavour=eni

In response to this:

/test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[tityosbot]

@tuladhar: The following test failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
e2e	633957a	link	/test e2e region=default flavour=default

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[tityosbot]

@tuladhar: The following test failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
e2e	633957a	link	/test e2e region=default flavour=default

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.