infra
/
crds-catalog
1
0
Fork 0
Code Issues 1 Pull Requests Releases Activity

chore(deps): update dependency cert-manager/cert-manager to v1.11.1 #10

Merged
renovator merged 1 commits from renovate/crds-catalog into main 2023-04-07 16:32:19 +02:00
Conversation 0 Commits 1 Files Changed 1 +1 -1
renovator commented 2023-04-07 16:02:18 +02:00
Member
Copy Link

This PR contains the following updates:

Package Update Change
cert-manager/cert-manager patch v1.11.0 -> v1.11.1

Release Notes

cert-manager/cert-manager

v1.11.1

Compare Source

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)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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 Renovate Bot.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [cert-manager/cert-manager](https://github.com/cert-manager/cert-manager) | patch | `v1.11.0` -> `v1.11.1` | --- ### Release Notes <details> <summary>cert-manager/cert-manager</summary> ### [`v1.11.1`](https://github.com/cert-manager/cert-manager/releases/tag/v1.11.1) [Compare Source](https://github.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 ([#&#8203;5815](https://github.com/cert-manager/cert-manager/issues/5815), [@&#8203;SgtCoDFish](https://github.com/SgtCoDFish)) - Bump the distroless base images ([#&#8203;5930](https://github.com/cert-manager/cert-manager/issues/5930), [@&#8203;maelvls](https://github.com/maelvls)) - The auto-retry mechanism added in VCert 4.23.0 and part of cert-manager 1.11.0 ([#&#8203;5674](https://github.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. ([#&#8203;5819](https://github.com/cert-manager/cert-manager/issues/5819), [@&#8203;maelvls](https://github.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. ([#&#8203;5726](https://github.com/cert-manager/cert-manager/issues/5726), [@&#8203;SgtCoDFish](https://github.com/SgtCoDFish)) ##### Other (Cleanup or Flake) - Bump keystore-go to v4.4.1 to work around an upstream rewrite of history ([#&#8203;5730](https://github.com/cert-manager/cert-manager/issues/5730), [@&#8203;SgtCoDFish](https://github.com/SgtCoDFish)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNS4zNS4wIiwidXBkYXRlZEluVmVyIjoiMzUuMzUuMCJ9-->
renovator added 1 commit 2023-04-07 16:02:19 +02:00
continuous-integration/drone/pr Build is passing Details
continuous-integration/drone/push Build is passing Details
e0af06f0da chore(deps): update dependency cert-manager/cert-manager to v1.11.1
renovator merged commit e0af06f0da into main 2023-04-07 16:32:19 +02:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: infra/crds-catalog#10
No description provided.
Delete Branch "renovate/crds-catalog"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?