Bump the all group with 4 updates

[dependabot]

Bumps the all group with 4 updates: github.com/cert-manager/cert-manager, golang.org/x/exp, k8s.io/utils and sigs.k8s.io/controller-runtime.

Updates github.com/cert-manager/cert-manager from 1.14.5 to 1.15.0

Release notes

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

v1.15.0

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

cert-manager 1.15 promotes several features to beta, including GatewayAPI support (ExperimentalGatewayAPISupport), the ability to provide a subject in the Certificate that will be used literally in the CertificateSigningRequest (LiteralCertificateSubject) and the outputting of additional certificate formats (AdditionalCertificateOutputFormats).

[!NOTE]

The cmctl binary have been moved to https://github.com/cert-manager/cmctl/releases. For the startupapicheck Job you should update references to point at quay.io/jetstack/cert-manager-startupapicheck

[!NOTE]

From this release, the Helm chart will no longer uninstall the CRDs when the chart is uninstalled. If you want the CRDs to be removed on uninstall use crds.keep=false when installing the Helm chart.

Community

Thanks again to all open-source contributors with commits in this release, including: @​Pionerd, @​SgtCoDFish, @​ThatsMrTalbot, @​andrey-dubnik, @​bwaldrep, @​eplightning, @​erikgb, @​findnature, @​gplessis, @​import-shiburin, @​inteon, @​jkroepke, @​lunarwhite, @​mangeshhambarde, @​pwhitehead-splunk & @​rodrigorfk, @​wallrj.

Thanks also to the following cert-manager maintainers for their contributions during this release: @​SgtCoDFish, @​SpectralHiss, @​ThatsMrTalbot, @​hawksight, @​inteon, @​maelvls & @​wallrj.

Equally thanks to everyone who provided feedback, helped users and raised issues on GitHub and Slack and joined our meetings!

Thanks also to the CNCF, which provides resources and support, and to the AWS open source team for being good community members and for their maintenance of the PrivateCA Issuer.

In addition, massive thanks to Venafi for contributing developer time and resources towards the continued maintenance of cert-manager projects.

Changes by Kind

Feature

• GatewayAPI support has graduated to Beta. Add the --enable-gateway-api flag to enable the integration. (#6961, @​ThatsMrTalbot)
• Add support to specify a custom key alias in a JKS Keystore (#6807, @​bwaldrep)
• Add the ability to communicate with Vault via mTLS when strict client certificates is enabled at Vault server side (#6614, @​rodrigorfk)
• Added option to provide additional audiences in the service account auth section for vault (#6718, @​andrey-dubnik)
• Venafi Issuer now sends a cert-manager HTTP User-Agent header in all Venafi Rest API requests. For example: cert-manager-certificaterequests-issuer-venafi/v1.15.0+(linux/amd64)+cert-manager/ef068a59008f6ed919b98a7177921ddc9e297200. (#6865, @​wallrj)
• Add hint to validation error message to help users of external issuers more easily fix the issue if they specify a Kind but forget the Group (#6913, @​SgtCoDFish)
• Add support for numeric OID types in LiteralSubject. Eg. "1.2.3.4=String Value" (#6775, @​inteon)
• Promote the LiteralCertificateSubject feature to Beta. (#7030, @​inteon)
• Promoted the AdditionalCertificateOutputFormats feature gate to Beta (enabled by default). (#6970, @​erikgb)
• The Helm chart now allows you to supply extraObjects; a list of yaml manifests which will helm will install and uninstall with the cert-manager manifests. (#6424, @​gplessis)
• Update the Route53 provider to support fetching credentials using AssumeRoleWithWebIdentity (#6878, @​pwhitehead-splunk)
• Helm can now add optional hostAliases to cert-manager Pod to allow the DNS self-check to pass in custom scenarios. (#6456, @​Pionerd)
• Added a new Ingress annotation for copying specific Ingress annotations to Certificate's secretTemplate (#6839, @​mangeshhambarde)
• Added option to define additional token audiences for the Vault Kubernetes auth (#6744, @​andrey-dubnik)
• Allow cert-manager.io/allow-direct-injection in annotations (#6801, @​jkroepke)

Design

• Remove repetitive words (#6949, @​findnature)

... (truncated)

Commits

• 3403251 Merge pull request #7055 from cert-manager-bot/cherry-pick-7052-to-release-1.15
• b1ac915 Merge pull request #7054 from cert-manager-bot/cherry-pick-7049-to-release-1.15
• c392ea8 BUGFIX: correctly mount config files for components
• dfce6b9 if list of controllers only contains disabled controllers, implicitly enable ...
• dadd37d run 'make generate-helm-docs'
• c92fb1c add Helm options to extend auto-approval or disable it
• d3e8db7 Merge pull request #7050 from cert-manager/self-upgrade-release-1.15
• 8f475f6 BOT: run 'make upgrade-klone' and 'make generate'
• ebb5281 Merge pull request #7044 from inteon/fix_release_bug
• 64676af Merge pull request #7034 from cert-manager/self-upgrade-master
• Additional commits viewable in compare view

Updates golang.org/x/exp from 0.0.0-20240416160154-fe59bbe5cc7f to 0.0.0-20240506185415-9bf2ced13842

Commits

• See full diff in compare view

Updates k8s.io/utils from 0.0.0-20240423183400-0849a56e8f22 to 0.0.0-20240502163921-fe8a2dddb1d0

Commits

• See full diff in compare view

Updates sigs.k8s.io/controller-runtime from 0.18.3 to 0.18.4

Release notes

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

v0.18.4

What's Changed

• [release-0.18] ✨ controllerutil: configure BlockOwnerDeletion when setting OwnerReference by @​k8s-infra-cherrypick-robot in kubernetes-sigs/controller-runtime#2848

Full Changelog: kubernetes-sigs/controller-runtime@v0.18.3...v0.18.4

Commits

• 12cc8d5 Merge pull request #2848 from k8s-infra-cherrypick-robot/cherry-pick-2847-to-...
• c0c229e controllerutil: allow configuring BlockOwnerDeletion when setting OwnerRefere...
• 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]

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

[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

[inteon]

/lgtm