chore(deps): bump github.com/cert-manager/cert-manager from 1.14.4 to 1.15.4

[dependabot]

Bumps github.com/cert-manager/cert-manager from 1.14.4 to 1.15.4.

Release notes

Sourced from github.com/cert-manager/cert-manager's releases.

v1.15.4

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

This patch release of cert-manager 1.15 makes several changes to how PEM input is validated, adding maximum sizes appropriate to the type of PEM data which is being parsed.

This is to prevent an unacceptable slow-down in parsing specially crafted PEM data. The issue was found by Google's OSS-Fuzz project.

The issue is low severity; to exploit the PEM issue would require privileged access which would likely allow Denial-of-Service through other methods.

Note also that since most PEM data parsed by cert-manager comes from ConfigMap or Secret resources which have a max size limit of approximately 1MB, it's difficult to force cert-manager to parse large amounts of PEM data.

Further information is available in GHSA-r4pg-vg54-wxx4

In addition, the version of Go used to build cert-manager 1.15 was updated along with the base images, and a Route53 bug fix was backported.

Changes by Kind

Bug or Regression

• Bugfix: Prevent aggressive Route53 retries caused by STS authentication failures by removing the Amazon Request ID from STS errors. (#7261, @​cert-manager-bot)
• Set a maximum size for PEM inputs which cert-manager will accept to remove possibility of taking a long time to process an input (#7402, @​SgtCoDFish)

Other (Cleanup or Flake)

• Bump go to 1.22.9 (#7424, @​SgtCoDFish)
• Upgrade Go to 1.22.8, the latest available patch release (#7406, @​SgtCoDFish)

v1.15.3

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

🔗 See v1.15.0 for more information about cert-manager 1.15 and read-before-upgrade info.

📜 Changes since v1.15.2

Bug or Regression

• BUGFIX: the dynamic certificate source used by the webhook TLS server failed to detect a root CA approaching expiration, due to a calculation error. This will cause the webhook TLS server to fail renewing its CA certificate. Please upgrade before the expiration of this CA certificate is reached. (#7232, @​cert-manager-bot)

v1.15.2

cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.

🔗 See v1.15.0 for more information about cert-manager 1.15 and read-before-upgrade info.

📜 Changes since v1.15.1

Bug or Regression

• BUGFIX route53: explicitly set the aws-global STS region which is now required by the github.com/aws/aws-sdk-go-v2 library. (#7189, @cert-manager-bot)
• Bump grpc-go to fix GHSA-xr7q-jx4m-x55m (#7167, @SgtCoDFish)
• Fix Azure DNS causing panics whenever authentication error happens (#7188, @cert-manager-bot)

... (truncated)

Commits

• 85dd399 Merge pull request #7424 from SgtCoDFish/release-1.15-bumps
• 4554fab [release-1.15] bump go + base images
• 8d2bc2d Merge pull request #7406 from SgtCoDFish/release-1.15-bumps
• 6adb6df Merge pull request #7402 from SgtCoDFish/release-1.15-pem-inputs
• 97aae04 update go version, base images
• 0792f09 security: remove calls to pem.Decode in non-test code
• 7fc813f security: Add functions to limit max PEM sizes allowable
• c84199d Merge pull request #7371 from SgtCoDFish/release-1.15-ipv6-dns
• 7cfce05 [release-1.15] add IPv6 example for recursive DNS arg
• 3155085 Merge pull request #7305 from SgtCoDFish/release-1.15-moretesting
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign anandf for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a redhat-developer member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[jgwest]

/ok-to-test

[openshift-ci]

@dependabot[bot]: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/unit	28d00e9	link	true	/test unit
ci/prow/v4.17-ci-index-gitops-operator-bundle	28d00e9	link	true	/test v4.17-ci-index-gitops-operator-bundle
ci/prow/v4.17-images	28d00e9	link	true	/test v4.17-images
ci/prow/v4.12-ci-index-gitops-operator-bundle	28d00e9	link	true	/test v4.12-ci-index-gitops-operator-bundle
ci/prow/v4.17-kuttl-sequential	28d00e9	link	true	/test v4.17-kuttl-sequential
ci/prow/v4.17-e2e	28d00e9	link	true	/test v4.17-e2e
ci/prow/v4.17-kuttl-parallel	28d00e9	link	true	/test v4.17-kuttl-parallel
ci/prow/v4.12-kuttl-sequential	28d00e9	link	true	/test v4.12-kuttl-sequential
ci/prow/v4.12-e2e	28d00e9	link	true	/test v4.12-e2e
ci/prow/v4.12-kuttl-parallel	28d00e9	link	true	/test v4.12-kuttl-parallel
ci/prow/v4.12-images	28d00e9	link	true	/test v4.12-images

Full PR test history. Your PR dashboard.

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-sigs/prow repository. I understand the commands that are listed here.