Bump github.com/cert-manager/cert-manager from 1.8.0 to 1.11.1

[dependabot]

Bumps github.com/cert-manager/cert-manager from 1.8.0 to 1.11.1.

Release notes

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

v1.11.1

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

In v1.11.1, we updated the base images used for cert-manager containers. In addition, the users of the Venafi issuer will see less certificates repeatedly failing.

If you are a user of Venafi TPP and have been having issues with the error message This certificate cannot be processed while it is in an error state. Fix any errors, and then click Retry, please use this version.

Changes since v1.11.0

Bug or Regression

• Bump helm and other dependencies to fix CVEs, along with upgrading go and base images (#5815, @​SgtCoDFish)
• Bump the distroless base images (#5930, @​maelvls)
• The auto-retry mechanism added in VCert 4.23.0 and part of cert-manager 1.11.0 (#5674) has been found to be faulty. Until this issue is fixed upstream, we now use a patched version of VCert. This patch will slowdown the issuance of certificates by 9% in case of heavy load on TPP. We aim to release at an ulterior date a patch release of cert-manager to fix this slowdown. (#5819, @​maelvls)
• Use a fake-kube apiserver version when generating helm template in cmctl x install, to work around a hardcoded Kubernetes version in Helm. (#5726, @​SgtCoDFish)

Other (Cleanup or Flake)

• Bump keystore-go to v4.4.1 to work around an upstream rewrite of history (#5730, @​SgtCoDFish)

v1.11.1-beta.0

⚠️ cert-manager v1.11.1-beta.0 is a pre-release patch version intended for testing and might not be suitable for production uses.

If you are a user of Venafi TPP and have been having issues with the error message This certificate cannot be processed while it is in an error state. Fix any errors, and then click Retry, please try this version.

Changes since v1.11.0

Bug or Regression

• The auto-retry mechanism added in VCert 4.23.0 and part of cert-manager 1.11.0 (#5674) has been found to be faulty. Until this issue is fixed upstream, we now use a patched version of VCert. This patch will slowdown the issuance of certificates by 9% in case of heavy load on TPP. We aim to release at an ulterior date a patch release of cert-manager to fix this slowdown. (#5819, @​maelvls)
• Use a fake kube apiserver version when generating helm template in cmctl x install, to work around a hardcoded Kubernetes version in Helm. (#5726, @​SgtCoDFish)
• Bump helm and other dependencies to fix CVEs, along with upgrading go and base images (#5815, @​SgtCoDFish)

Other

• Bump keystore-go to v4.4.1 to work around an upstream rewrite of history (#5730, @​SgtCoDFish)

v1.11.0

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

v1.11.0 includes a drastic reduction in cert-manager's runtime memory usage, a slew of improvements to AKS integrations and various other tweaks, fixes and improvements, all towards cert-manager's goal of being the best way to handle certificates in modern Cloud Native applications.

Community

Thanks again to all open-source contributors with commits in this release, including:

• @​cmcga1125
• @​karlschriek
• @​lvyanru8200
• @​mmontes11

... (truncated)

Commits

• e3a2a80 Merge pull request #5930 from maelvls/bump-distroless-1.11
• b16cbc9 Bump distroless base images and kind versions
• fe544bf Merge pull request #5857 from jetstack-bot/cherry-pick-5812-to-release-1.11
• e1a5457 make: force the use of registry.k8s.io by ingressnginx
• 87fa565 update k8s.gcr.io to registry.k8s.io
• 785c311 Merge pull request #5819 from maelvls/backport-1.11
• 8b6b8cd use jetstack vcert fork to properly reset on error for TPP
• 1ff4238 Merge pull request #5815 from SgtCoDFish/release-1.11-bumphelm
• 19259ae bump go version
• 29757f7 update base images to latest
• 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 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)

[rkosegi]

@dependabot rebase