Bump the all group across 1 directory with 13 updates

[dependabot]

Bumps the all group with 10 updates in the / directory:

Package	From	To
github.com/cert-manager/cert-manager	1.15.3	1.16.1
github.com/cert-manager/csi-lib	0.7.0	0.8.0
github.com/onsi/ginkgo/v2	2.20.2	2.21.0
github.com/onsi/gomega	1.34.2	1.35.1
golang.org/x/sync	0.8.0	0.9.0
k8s.io/api	0.31.1	0.31.2
k8s.io/cli-runtime	0.31.1	0.31.2
k8s.io/component-base	0.31.1	0.31.2
k8s.io/kubectl	0.31.1	0.31.2
sigs.k8s.io/controller-runtime	0.19.0	0.19.1

Updates github.com/cert-manager/cert-manager from 1.15.3 to 1.16.1

Release notes

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

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.
2. ACME DNS01 ClusterIssuer fail while loading credentials from Secret resources.

❗ 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)

... (truncated)

Commits

• ff50c06 Merge pull request #7356 from cert-manager-bot/cherry-pick-7350-to-release-1.16
• 2298278 Helm: add enabled to json schema
• 02f4a60 Merge pull request #7355 from cert-manager-bot/cherry-pick-7351-to-release-1.16
• 7525267 Helm chart: fix documentation for service accounts annotations
• b44f375 Merge pull request #7348 from cert-manager/self-upgrade-release-1.16
• c3bdc1f Run 'make upgrade-klone' and 'make generate'
• 2d22a92 Merge pull request #7345 from cert-manager-bot/cherry-pick-7343-to-release-1.16
• 4f4ea8b update schema validation for minAvailable and maxAvailable to accept both str...
• 17d9d81 Merge pull request #7342 from cert-manager-bot/cherry-pick-7339-to-release-1.16
• 1144aab add ACME ClusterIssuer resource namespace test
• Additional commits viewable in compare view

Updates github.com/cert-manager/csi-lib from 0.7.0 to 0.8.0

Release notes

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

v0.8.0

What's Changed

• Replace deprecated functions and add missing error checks by @​inteon in cert-manager/csi-lib#64
• Update atomic writer based on upstream: avoiding chown race condition by @​inteon in cert-manager/csi-lib#65
• Upgrade golang 1.23 and support CSI spec v1.10.0 by @​7ing in cert-manager/csi-lib#67

Full Changelog: cert-manager/csi-lib@v0.7.0...v0.8.0

Commits

• c552f3a Merge pull request #67 from 7ing/upgrade-go-1.23
• f64c593 Upgrade golang 1.23 and support CSI spec v1.10.0
• bff7666 Merge pull request #65 from inteon/update_atomic_writer
• 3ba2694 Merge pull request #64 from inteon/replace_deprecated
• 1f84151 update vendored atomic writer to latest upstream version
• ffb1d38 replace deprecated functions and add missing error checks
• See full diff in compare view

Updates github.com/onsi/ginkgo/v2 from 2.20.2 to 2.21.0

Release notes

Sourced from github.com/onsi/ginkgo/v2's releases.

v2.21.0

2.21.0

Features

• add support for GINKGO_TIME_FORMAT [a69eb39]
• add GINKGO_NO_COLOR to disable colors via environment variables [bcab9c8]

Fixes

• increase threshold in timeline matcher [e548367]
• Fix the document by replacing SpecsThatWillBeRun with SpecsThatWillRun [c2c4d3c]

Maintenance

• bump various dependencies [7e65a00]

Changelog

Sourced from github.com/onsi/ginkgo/v2's changelog.

2.21.0

Features

• add support for GINKGO_TIME_FORMAT [a69eb39]
• add GINKGO_NO_COLOR to disable colors via environment variables [bcab9c8]

Fixes

• increase threshold in timeline matcher [e548367]
• Fix the document by replacing SpecsThatWillBeRun with SpecsThatWillRun [c2c4d3c]

Maintenance

• bump various dependencies [7e65a00]

Commits

• ac8918e v2.21.0
• a69eb39 add support for GINKGO_TIME_FORMAT
• e548367 increase threshold in timeline matcher
• bcab9c8 add GINKGO_NO_COLOR to disable colors via environment variables
• 7e65a00 bump various dependencies
• c2c4d3c Fix the document by replacing SpecsThatWillBeRun with SpecsThatWillRun
• See full diff in compare view

Updates github.com/onsi/gomega from 1.34.2 to 1.35.1

Release notes

Sourced from github.com/onsi/gomega's releases.

v1.35.1

1.35.1

Fixes

• Export EnforceDefaultTimeoutsWhenUsingContexts and DisableDefaultTimeoutsWhenUsingContext [ca36da1]

v1.35.0

1.35.0

Features

• You can now call EnforceDefaultTimeoutsWhenUsingContexts() to have Eventually honor the default timeout when passed a context. (prior to this you had to expclility add a timeout) [e4c4265]
• You can call StopTrying(message).Successfully() to abort a Consistently early without failure [eeca931]

Fixes

• Stop memoizing the result of HaveField to avoid unexpected errors when used with async assertions. [3bdbc4e]

Maintenance

• Bump all dependencies [a05a416]

Changelog

Sourced from github.com/onsi/gomega's changelog.

1.35.1

Fixes

• Export EnforceDefaultTimeoutsWhenUsingContexts and DisableDefaultTimeoutsWhenUsingContext [ca36da1]

1.35.0

Features

• You can now call EnforceDefaultTimeoutsWhenUsingContexts() to have Eventually honor the default timeout when passed a context. (prior to this you had to expclility add a timeout) [e4c4265]
• You can call StopTrying(message).Successfully() to abort a Consistently early without failure [eeca931]

Fixes

• Stop memoizing the result of HaveField to avoid unexpected errors when used with async assertions. [3bdbc4e]

Maintenance

• Bump all dependencies [a05a416]

Commits

• 9f5a208 v1.35.1
• ca36da1 Export EnforceDefaultTimeoutsWhenUsingContexts and DisableDefaultTimeoutsWhen...
• d6331f9 v1.35.0
• 5deaf23 fix tests, but like actually this time
• eeca931 Add Successfully() to StopTrying() to signal that Consistently can end early ...
• 3bdbc4e stop memoizing result of HaveField
• e35358d sheepishly fix broken test. thanks CI
• 1b717d7 grrr. go mod tidy
• a05a416 bump all dependencies
• e4c4265 Add EnforceDefaultTimeoutsWhenUsingContexts()
• See full diff in compare view

Updates golang.org/x/sync from 0.8.0 to 0.9.0

Commits

• 151027e README: don't recommend go get
• See full diff in compare view

Updates k8s.io/api from 0.31.1 to 0.31.2

Commits

• bc73ef7 Update dependencies to v0.31.2 tag
• See full diff in compare view

Updates k8s.io/apimachinery from 0.31.1 to 0.31.2

Commits

• See full diff in compare view

Updates k8s.io/cli-runtime from 0.31.1 to 0.31.2

Commits

• 95d5f7c Update dependencies to v0.31.2 tag
• See full diff in compare view

Updates k8s.io/client-go from 0.31.1 to 0.31.2

Commits

• 270e5ab Update dependencies to v0.31.2 tag
• See full diff in compare view

Updates k8s.io/component-base from 0.31.1 to 0.31.2

Commits

• 0c667d6 Update dependencies to v0.31.2 tag
• See full diff in compare view

Updates k8s.io/kubectl from 0.31.1 to 0.31.2

Commits

• 5eafd70 Update dependencies to v0.31.2 tag
• See full diff in compare view

Updates k8s.io/utils from 0.0.0-20240711033017-18e509b52bc8 to 0.0.0-20240921022957-49e7df575cb6

Commits

• See full diff in compare view

Updates sigs.k8s.io/controller-runtime from 0.19.0 to 0.19.1

Release notes

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

v0.19.1

What's Changed

• [release-0.19] 🌱 Verify PR titles with shell script by @​k8s-infra-cherrypick-robot in kubernetes-sigs/controller-runtime#2947
• [release-0.19] 🐛 Fakeclient: preserve TypeMeta for PartialObjectMeta resources by @​k8s-infra-cherrypick-robot in kubernetes-sigs/controller-runtime#2951
• [release-0.19] 🌱 pr-verify: use env var for passing the PR title by @​k8s-infra-cherrypick-robot in kubernetes-sigs/controller-runtime#2962
• [release-0.19] 🌱 pr-verify: use env var for passing the PR title by @​k8s-infra-cherrypick-robot in kubernetes-sigs/controller-runtime#2965
• [release-0.19] 🌱 Fix PR verify action by @​k8s-infra-cherrypick-robot in kubernetes-sigs/controller-runtime#2974
• [release-0.19] 🐛 Fakeclient: Fix TOCTOU races by @​k8s-infra-cherrypick-robot in kubernetes-sigs/controller-runtime#2992

Full Changelog: kubernetes-sigs/controller-runtime@v0.19.0...v0.19.1

Commits

• 013f46f Merge pull request #2992 from k8s-infra-cherrypick-robot/cherry-pick-2980-to-...
• 4421425 bug: Fakeclient: Fix TOCTOU races
• aa14005 Merge pull request #2974 from k8s-infra-cherrypick-robot/cherry-pick-2973-to-...
• f883b25 Fix PR verify action
• 409ae31 Merge pull request #2965 from k8s-infra-cherrypick-robot/cherry-pick-2964-to-...
• 465b62a pr-verify: use env var for passing the PR title
• d32b491 Merge pull request #2962 from k8s-infra-cherrypick-robot/cherry-pick-2961-to-...
• b400366 pr-verify: use env var for passing the PR title
• 22d9eab Merge pull request #2951 from k8s-infra-cherrypick-robot/cherry-pick-2949-to-...
• f0e55af Preserve TypeMeta for PartialObjectMeta resources
• 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 <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]

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.

[inteon]

/approve
/lgtm

[inteon]

/approve
/lgtm

[inteon]

/approve
/lgtm

[cert-manager-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: inteon

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [inteon]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment