cert-manager/cert-manager
### [`v1.11.1`](https://togithub.com/cert-manager/cert-manager/releases/tag/v1.11.1)
[Compare Source](https://togithub.com/cert-manager/cert-manager/compare/v1.11.0...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](https://togithub.com/cert-manager/cert-manager/issues/5815), [@SgtCoDFish](https://togithub.com/SgtCoDFish))
- Bump the distroless base images ([#5930](https://togithub.com/cert-manager/cert-manager/issues/5930), [@maelvls](https://togithub.com/maelvls))
- The auto-retry mechanism added in VCert 4.23.0 and part of cert-manager 1.11.0 ([#5674](https://togithub.com/cert-manager/cert-manager/issues/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](https://togithub.com/cert-manager/cert-manager/issues/5819), [@maelvls](https://togithub.com/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](https://togithub.com/cert-manager/cert-manager/issues/5726), [@SgtCoDFish](https://togithub.com/SgtCoDFish))
##### Other (Cleanup or Flake)
- Bump keystore-go to v4.4.1 to work around an upstream rewrite of history ([#5730](https://togithub.com/cert-manager/cert-manager/issues/5730), [@SgtCoDFish](https://togithub.com/SgtCoDFish))
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
â™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
v1.11.0->v1.11.1Release Notes
cert-manager/cert-manager
### [`v1.11.1`](https://togithub.com/cert-manager/cert-manager/releases/tag/v1.11.1) [Compare Source](https://togithub.com/cert-manager/cert-manager/compare/v1.11.0...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](https://togithub.com/cert-manager/cert-manager/issues/5815), [@SgtCoDFish](https://togithub.com/SgtCoDFish)) - Bump the distroless base images ([#5930](https://togithub.com/cert-manager/cert-manager/issues/5930), [@maelvls](https://togithub.com/maelvls)) - The auto-retry mechanism added in VCert 4.23.0 and part of cert-manager 1.11.0 ([#5674](https://togithub.com/cert-manager/cert-manager/issues/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](https://togithub.com/cert-manager/cert-manager/issues/5819), [@maelvls](https://togithub.com/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](https://togithub.com/cert-manager/cert-manager/issues/5726), [@SgtCoDFish](https://togithub.com/SgtCoDFish)) ##### Other (Cleanup or Flake) - Bump keystore-go to v4.4.1 to work around an upstream rewrite of history ([#5730](https://togithub.com/cert-manager/cert-manager/issues/5730), [@SgtCoDFish](https://togithub.com/SgtCoDFish))Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
â™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.