build(deps): bump github.com/cert-manager/cert-manager from 1.13.6 to 1.16.0

[dependabot]

Bumps github.com/cert-manager/cert-manager from 1.13.6 to 1.16.0.

Release notes

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

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.

❗ Breaking changes

1. Helm schema validation may reject your existing Helm values files if they contain typos or unrecognized fields.
2. Venafi Issuer may fail to renew certificates if the requested duration conflicts with the CA’s minimum or maximum policy settings in Venafi.
3. Venafi Issuer may fail to renew Certificates if the issuer has been configured for TPP with username-password authentication.

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

📜 Changes since v1.15.0

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

Feature

• Add SecretRef support for Venafi TPP issuer CA Bundle (#7036, @sankalp-at-gh)
• Add renewBeforePercentage alternative to renewBefore (#6987, @cbroglie)
• Add a metrics server to the cainjector (#7194, @wallrj)
• Add a metrics server to the webhook (#7182, @wallrj)
• Add client certificate auth method for Vault issuer (#4330, @joshmue)
• Add process and go runtime metrics for controller (#6966, @mindw)
• Added app.kubernetes.io/managed-by: cert-manager label to the cert-manager-webhook-ca Secret (#7154, @jrcichra)
• Allow the user to specify a Pod template when using GatewayAPI HTTP01 solver, this mirrors the behavior when using the Ingress HTTP01 solver. (#7211, @ThatsMrTalbot)
• Create token request RBAC for the cert-manager ServiceAccount by default (#7213, @Jasper-Ben)
• Feature: Append cert-manager user-agent string to all AWS API requests, including IMDS and STS requests. (#7295, @wallrj)
• Feature: Log AWS SDK warnings and API requests at cert-manager debug level to help debug AWS Route53 problems in the field. (#7292, @wallrj)
• Feature: The Route53 DNS solver of the ACME Issuer will now use regional STS endpoints computed from the region that is supplied in the Issuer spec or in the AWS_REGION environment variable. Feature: The Route53 DNS solver of the ACME Issuer now uses the "ambient" region (AWS_REGION or AWS_DEFAULT_REGION) if issuer.spec.acme.solvers.dns01.route53.region is empty; regardless of the flags --issuer-ambient-credentials and --cluster-issuer-ambient-credentials. (#7299, @wallrj)
• Helm: adds JSON schema validation for the Helm values. (#7069, @inteon)
• If the --controllers flag only specifies disabled controllers, the default controllers are now enabled implicitly. Added disableAutoApproval and approveSignerNames Helm chart options. (#7049, @inteon)
• Make it easier to configure cert-manager using Helm by defaulting config.apiVersion and config.kind within the Helm chart. (#7126, @ThatsMrTalbot)
• Now passes down specified duration to Venafi client instead of using the CA default only. (#7104, @Guitarkalle)
• Reduce the memory usage of cainjector, by only caching the metadata of Secret resources. Reduce the load on the K8S API server when cainjector starts up, by only listing the metadata of Secret resources. (#7161, @wallrj)
• The Route53 DNS01 solver of the ACME Issuer can now detect the AWS region from the AWS_REGION and AWS_DEFAULT_REGION environment variables, which is set by the IAM for Service Accounts (IRSA) webhook and by the Pod Identity webhook. The issuer.spec.acme.solvers.dns01.route53.region field is now optional. The API documentation of the region field has been updated to explain when and how the region value is used. (#7287, @wallrj)
• Venafi TPP issuer can now be used with a username & password combination with OAuth. Fixes #4653. Breaking: cert-manager will no longer use the API Key authentication method which was deprecated in 20.2 and since removed in 24.1 of TPP. (#7084, @hawksight)
• You can now configure the pod security context of HTTP-01 solver pods. (#5373, @aidy)
• Helm: New value webhook.extraEnv, allows you to set custom environment variables in the webhook Pod. Helm: New value cainjector.extraEnv, allows you to set custom environment variables in the cainjector Pod. Helm: New value startupapicheck.extraEnv, allows you to set custom environment variables in the startupapicheck Pod. (#7319, @wallrj)

... (truncated)

Commits

• 67c897d Merge pull request #7325 from cert-manager-bot/cherry-pick-7323-to-release-1.16
• 3470785 make update-base-images
• f9e8aa6 Merge pull request #7324 from cert-manager-bot/cherry-pick-7321-to-release-1.16
• d09894c BOT: run 'make upgrade-klone' and 'make generate'
• f98340d Merge pull request #7319 from cert-manager-bot/cherry-pick-7317-to-release-1.16
• 78dd1bf Update deployments and startupapi Job
• 8c46145 make generate-helm-schema generate-helm-docs
• 99dc5d2 Add extraEnv to webhook, cainjector, and startupapicheck
• e381fb0 Merge pull request #7318 from cert-manager-bot/cherry-pick-7315-to-release-1.16
• 514f559 Revert "Reduce load on the Kubernetes API server and reduce the peak memory u...
• 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)

[dependabot]

Superseded by #960.