Bump the all group across 1 directory with 3 updates

[dependabot]

Bumps the all group with 3 updates in the / directory: github.com/cert-manager/cert-manager, google.golang.org/protobuf and sigs.k8s.io/controller-runtime.

Updates github.com/cert-manager/cert-manager from 1.16.0-beta.0.0.20250107112437-c422d5944196 to 1.16.2

Release notes

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

v1.16.2

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

This patch release of cert-manager 1.16 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.16 was updated along with the base images.

Changes by Kind

Bug or Regression

• Set a maximum size for PEM inputs which cert-manager will accept to remove possibility of taking a long time to process an input (#7401, @​SgtCoDFish)

Other (Cleanup or Flake)

• Bump go to 1.23.3 and bump base images to latest available (#7431, @​SgtCoDFish)

v1.16.1

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

The cert-manager 1.16 release includes: new Helm chart features, more Prometheus metrics, memory optimizations, and various improvements and bug fixes for the ACME issuer and Venafi Issuer.

📖 Read the complete 1.16 release notes before upgrading.

📜Changes since v1.16.0

Bug or Regression

• BUGFIX: Helm schema validation: the new schema validation was too strict for the "global" section. Since the global section is shared across all charts and sub-charts, we must also allow unknown fields. (#7348, @inteon)
• BUGFIX: Helm will now accept percentages for the podDisruptionBudget.minAvailable and podDisruptionBudget.maxAvailable values. (#7345, @inteon)
• Helm: allow enabled to be set as a value to toggle cert-manager as a dependency. (#7356, @inteon)
• BUGFIX: A change in v1.16.0 caused cert-manager's ACME ClusterIssuer to look in the wrong namespace for resources required for the issuance (e.g. credential Secrets). This is now fixed in v1.16.1. (#7342, @inteon)

v1.16.0

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

The cert-manager 1.16 release includes: new Helm chart features, more Prometheus metrics, memory optimizations, and various improvements and bug fixes for the ACME issuer and Venafi Issuer.

📖 Read the complete 1.16 release notes at cert-manager.io.

⚠️ Known issues

1. Helm Chart: JSON schema prevents the chart being used as a sub-chart on Rancher RKE.

... (truncated)

Commits

• See full diff in compare view

Updates google.golang.org/protobuf from 1.36.1 to 1.36.2

Updates sigs.k8s.io/controller-runtime from 0.19.3 to 0.19.4

Release notes

Sourced from sigs.k8s.io/controller-runtime's releases.

v0.19.4

What's Changed

• 🌱 Add fsnotify watcher+polling by @​sbueringer in kubernetes-sigs/controller-runtime#3052

Full Changelog: kubernetes-sigs/controller-runtime@v0.19.3...v0.19.4

Commits

• 7436275 Merge pull request #3052 from sbueringer/cert-watcher-plus-0.19
• 3218a86 adjust tests
• 3c5359d Add fsnotify watcher+polling
• See full diff 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[cert-manager-prow]

[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 wallrj 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

[cert-manager-prow]

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

I'm waiting for a cert-manager 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.

[SgtCoDFish]

/hold

This is interesting - this isn't actually correct since the version of cert-manager here wouldn't use the "fixed" version of cert-manager from the master branch, which was explicitly chosen in #477

[SgtCoDFish]

This is interesting - this isn't actually correct since the version of cert-manager here wouldn't use the "fixed" version of cert-manager from the master branch

Following onto this - govulncheck actually is failing for this, because it doesn't see that the fixed version of the code (on the master branch) is actually newer than the v1.16.0 tag.

Probably the solution here is to tag cert-manager v1.17.0-alpha.0 and use that as the version we depend on here in istio-csr.

EDIT: Since I'll be releasing an alpha of 1.17.0 soon, I'll wait until I've done that and pointed istio-csr at it before unholding this.

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.