fix(deps): update module github.com/cert-manager/cert-manager to v1.17.0

[ibm-mend-app]

This PR contains the following updates:

Package	Type	Update	Change
github.com/cert-manager/cert-manager	require	minor	v1.15.3 -> v1.17.0

---

Release Notes

cert-manager/cert-manager (github.com/cert-manager/cert-manager)

v1.17.0

Compare Source

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

v1.17.0 is a feature release with several improvements, including:

• A helpful compliance change to RSA signatures on certificates
• An easier way to specify passwords for PKCS#12 and JKS keystores
• A few feature flag promotions (and a deprecation)
• Dependency bumps and other smaller improvements

Major Themes

RSA Certificate Compliance

The United States Department of Defense published a memo in 2022 which introduced some requirements on the kinds of cryptography they require to be supported in software they use.

In effect, the memo requires that software be able to support larger RSA keys (3072-bit and 4096-bit) and hashing algorithms (SHA-384 at a minimum).

cert-manager supported large RSA keys long before the memo was published, but a quirk in implementation meant that cert-manager always used SHA-256 when signing with RSA.

In v1.17.0, cert-manager will choose a hash algorithm based on the RSA key length: 3072-bit keys will use SHA-384, and 4096-bit keys will use SHA-512. This matches similar behavior already present for ECDSA signatures.

Our expectation is that this change will have minimal impact beyond a slight increase to security and better compliance; we're not aware of Kubernetes based environments which support RSA 2048 with SHA-256 but fail with RSA 4096 and SHA-512. However, if you're using larger RSA keys, you should be aware of the change.

Easier Keystore Passwords for PKCS#12 and JKS

Specifying passwords on PKCS#12 and JKS keystores is supported in cert-manager
for compatibility reasons with software which expects or requires passwords to be set; however, these passwords are not relevant to security and never have been in cert-manager.

The initial implementation of the keystores feature required these "passwords" to be stored in a Kubernetes secret, which would then be read by cert-manager when creating the keystore after a certificate was issued. This is cumbersome, especially when many passwords are set to default values such as changeit or password.

In cert-manager v1.17, it's now possible to set a keystore password using a literal string value inside the Certificate resource itself, making this process much easier with no change to security.

For example:

apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
  name: my-cert-password
spec:
  secretName: my-cert-password
  issuerRef:
    name: my-issuer
    kind: ClusterIssuer
  keystores:
    jks:
      create: true
      password: "abc123"
    pkcs12:
      create: true
      password: "password"
  dnsNames:
  - example.com

The new password field is mutually exclusive with the passwordSecretRef field, so be sure to only set one.

Feature Flag Promotions / Deprecations

cert-manager's feature flags allow for easier testing and adoption of new features with a reduced risk of breaking changes. In cert-manager v1.17, two feature gates have been promoted to "beta", and as such are now enabled by default in all installations:

• NameConstraints, allowing users to specify the name constraints extension which can be helpful when creating CA certificates for private PKI
• UseDomainQualifiedFinalizer, which stops a Kubernetes warning from being printed in logs

In addition, we added a new feature gate: CAInjectorMerging, which intelligently combines certificates used by the CAInjector component, making it safer to use when issuing certificates are rotated. If you're making heavy use of the CA injector, you should consider enabling this feature gate.

Finally, we deprecated the ValidateCAA feature gate which will be removed entirely in cert-manager v1.18.0. This feature gate aimed to validate the CAA DNS record during ACME issuance, but has seen low adoption and limited testing since its introduction back in 2019.

Other Changes

There are many other PRs which were merged in this release cycle and we'd encourage you to read the release notes below. One PR that's worth highlighting is a change to add more structured logging information to certain log lines.

If you were previously filtering logs using grep or similar tools (which is highly discouraged!) be aware that some log lines have changed format.

Community

As always, we'd like to thank all of the community members who helped in this release cycle, including all below who merged a PR and anyone that helped by commenting on issues, testing, or getting involved in cert-manager meetings. We're lucky to have you involved.

A special thanks to:

• @​hawksight
• @​aidy
• @​bashlion
• @​7ing
• @​fadecore
• @​schedin
• @​jkroepke
• @​sdarwin

for their contributions, comments and support!

Also, thanks to the cert-manager maintainer team for their help in this release:

• @​inteon
• @​erikgb
• @​SgtCoDFish
• @​ThatsMrTalbot
• @​munnerz
• @​maelvls

And finally, thanks to the cert-manager steering committee for their feedback in this release cycle:

• @​FlorianLiebhart
• @​ssyno
• @​ianarsenault
• @​TrilokGeer

Changes by Kind

Feature

• Potentially BREAKING: The CA and SelfSigned issuers now use SHA-512 when signing with RSA keys 4096 bits and above, and SHA-384 when signing with RSA keys 3072 bits and above. If you were previously using a larger RSA key as a CA, be sure to check that your systems support the new hash algorithms. (#​7368, @​SgtCoDFish)
• Add CAInjectorMerging feature gate to the ca-injector, enabling this will change the behaviour of the ca-injector to merge in new CA certificates instead of outright replacing the existing one. (#​7469, @​ThatsMrTalbot)
• Added image pull secrets to deployments when service accounts aren't created (#​7411, @​TheHenrick)
• Added the ability to customize client ID when using username/password authentication for Venafi client (#​7484, @​ilyesAj)
• 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. (#​7317, @​wallrj)
• Increase the amount of PEM data pki.DecodeX509CertificateSetBytes is able to parse, to enable reading larger TLS trust bundles (#​7464, @​SgtCoDFish)
• New configuration option tenantID for the AzureDNS provider when using managed identities with service principals. This enhancement allows users to specify the tenant ID when using managed identities, offering better flexibility in multi-tenant environments. (#​7376, @​jochenrichter)
• Promote the UseDomainQualifiedFinalizer feature to Beta. (#​7488, @​jsoref)
• Allow JKS/PKCS12 keystore passwords to be set as literal values in Certificate resources, mutually exclusive with the existing passwordSecretRef field (#​6657, @​rquinio1A)
• Allow templating ServiceAccount annotations by running the built-in Helm tpl function on keys and values, to aid with workload identity configuration (#​7501, @​fcrespofastly)
• Promote CA NameConstraints feature gate to Beta (enabled by default) (#​7494, @​tanujd11)

Documentation

• Add example for IPv6 in --dns01-recursive-nameservers (#​7367, @​SgtCoDFish)
• Updated the chart documentation to show enableGatewayAPI in the config example. (#​7354, @​puerco)

Bug or Regression

• 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 (eg. credential Secrets). This is now fixed in v1.16.1+ and v1.17.0+ (#​7339, @​inteon)
• BUGFIX: Helm will now accept percentages for the podDisruptionBudget.minAvailable and podDisruptionBudget.maxAvailable values. (#​7343, @​inteon)
• Fix ACME HTTP-01 solver for IPv6 endpoints (#​7391, @​Peac36)
• Fix the behavior of renewBeforePercentage to comply with its spec (#​7421, @​adam-sroka)
• Helm: allow enabled to be set as a value to toggle cert-manager as a dependency. (#​7350, @​inteon)
• SECURITY (low risk): Limit maximum allowed PEM size to prevent potential DoS in cert-manager controller from attacker-controlled PEM. See GHSA-r4pg-vg54-wxx4 (#​7400, @​SgtCoDFish)
• The Certificate object will no longer create CertificateRequest or Secret objects while being deleted (#​7361, @​ThatsMrTalbot)
• The issuer will now more quickly retry when its linked Secret is updated to fix an issue that caused a high back-off timeout. (#​7455, @​inteon)
• Upgrades Venafi vCert library fixing a bug which caused the RSA 3072 bit key size for TPP certificate enrollment to not work. (#​7498, @​inteon)

Other (Cleanup or Flake)

• ⚠️ Potentially BREAKING: Log messages that were not structured have now been replaced with structured logs. If you were matching on specific log strings, this could break your setup. (#​7461, @​inteon)
• DEPRECATION: The ValidateCAA feature gate is now deprecated, with removal scheduled for cert-manager 1.18. In 1.17, enabling this feature gate will print a warning. (#​7491, @​jsoref)
• Remove Neither --kubeconfig nor --master was specified warning message when the controller and the webhook services boot (#​7457, @​Peac36)
• Move 'live' DNS tests into a separate package to contain test flakiness and improve developer UX (#​7530, @​SgtCoDFish)

v1.16.3

Compare Source

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

v1.16.3 is a patch release mainly focused around bumping dependencies to address reported CVEs: CVE-2024-45337 and CVE-2024-45338.

We don't believe that cert-manager is actually vulnerable; this release is instead intended to satisfy vulnerability scanners.

It also includes a bug fix to the new renewBeforePercentage field. If you were using renewBeforePercentage, see PR #​7421 for more information.

Changes

Bug

• Bump golang.org/x/net and golang.org/x/crypto to address CVE-2024-45337 and CVE-2024-45338 (#​7485, @​erikgb)
• Fix the behaviour of renewBeforePercentage to comply with its spec (#​7441, @​cert-manager-bot)

Other

• Bump go to 1.23.4 (#​7489, @​erikgb)
• Bump base images to latest available (#​7508, @​SgtCoDFish)

v1.16.2

Compare Source

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

Compare Source

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

Compare Source

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

Bug or Regression

• Adds support (behind a flag) to use a domain qualified finalizer. If the feature is enabled (which is not by default), it should prevent Kubernetes from reporting: metadata.finalizers: "finalizer.acme.cert-manager.io": prefer a domain-qualified finalizer name to avoid accidental conflicts with other finalizer writers (#​7273, @jsoref)
• BUGFIX Route53: explicitly set the aws-global STS region which is now required by the github.com/aws/aws-sdk-go-v2 library. (#​7108, @inteon)
• BUGFIX: fix issue that caused Vault issuer to not retry signing when an error was encountered. (#​7105, @inteon)
• BUGFIX: the dynamic certificate source used by the webhook TLS server failed to detect a root CA approaching expiration, due to a calculation error. This will cause the webhook TLS server to fail renewing its CA certificate. Please upgrade before the expiration of this CA certificate is reached. (#​7230, @inteon)
• Bugfix: Prevent aggressive Route53 retries caused by IRSA authentication failures by removing the Amazon Request ID from errors wrapped by the default credential cache. (#​7291, @wallrj)
• Bugfix: Prevent aggressive Route53 retries caused by STS authentication failures by removing the Amazon Request ID from STS errors. (#​7259, @wallrj)
• Bump grpc-go to fix GHSA-xr7q-jx4m-x55m (#​7164, @SgtCoDFish)
• Bump the go-retryablehttp dependency to fix CVE-2024-6104 (#​7125, @SgtCoDFish)
• Fix Azure DNS causing panics whenever authentication error happens (#​7177, @eplightning)
• Fix incorrect indentation of endpointAdditionalProperties in the PodMonitor template of the Helm chart (#​7190, @wallrj)
• Fixes ACME HTTP01 challenge behavior when using Gateway API to prevent unbounded creation of HTTPRoute resources (#​7178, @miguelvr)
• Handle errors arising from challenges missing from the ACME server (#​7202, @bdols)
• Helm BUGFIX: the cainjector ConfigMap was not mounted in the cainjector deployment. (#​7052, @inteon)
• Improve the startupapicheck: validate that the validating and mutating webhooks are doing their job. (#​7057, @inteon)
• The KeyUsages X.509 extension is no longer added when there are no key usages set (in accordance to RFC 5280 Section 4.2.1.3) (#​7250, @inteon)
• Update github.com/Azure/azure-sdk-for-go/sdk/azidentity to address CVE-2024-35255 (#​7087, @dependabot[bot])

Other (Cleanup or Flake)

• Old API versions were removed from the codebase.
  Removed:
  (acme.)cert-manager.io/v1alpha2
  (acme.)cert-manager.io/v1alpha3
  (acme.)cert-manager.io/v1beta1 (#​7278, @inteon)
• Upgrading to client-go v0.31.0 removes a lot of noisy reflector.go: unable to sync list result: internal error: cannot cast object DeletedFinalStateUnknown errors from logs. (#​7237, @inteon)
• Bump Go to v1.23.2 (#​7324, @cert-manager-bot)

v1.15.5

Compare Source

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

cert-manager v1.15.5 contains simple dependency bumps to address reported CVEs (CVE-2024-45337 and CVE-2024-45338).

We don't believe that cert-manager is actually vulnerable; this release is instead intended to satisfy vulnerability scanners.

Changes

Bug or Regression

• Bump golang.org/x/net to address CVE-2024-45337 and CVE-2024-45338 (#​7496, @​wallrj)

Other (Cleanup or Flake)

• Bump to go 1.22.10 (#​7507, @​SgtCoDFish)

v1.15.4

Compare Source

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

This patch release of cert-manager 1.15 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.15 was updated along with the base images, and a Route53 bug fix was backported.

Changes by Kind

Bug or Regression

• Bugfix: Prevent aggressive Route53 retries caused by STS authentication failures by removing the Amazon Request ID from STS errors. (#​7261, @​cert-manager-bot)
• Set a maximum size for PEM inputs which cert-manager will accept to remove possibility of taking a long time to process an input (#​7402, @​SgtCoDFish)

Other (Cleanup or Flake)

• Bump go to 1.22.9 (#​7424, @​SgtCoDFish)
• Upgrade Go to 1.22.8, the latest available patch release (#​7406, @​SgtCoDFish)

---

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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

[ibm-mend-app]

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 45 additional dependencies were updated
• The go directive was updated for compatibility reasons

Details:

Package	Change
go	1.23.0 -> 1.23.4
k8s.io/apiextensions-apiserver	v0.30.5 -> v0.32.0
k8s.io/client-go	v0.30.5 -> v0.32.0
github.com/fsnotify/fsnotify	v1.7.0 -> v1.8.0
github.com/google/cel-go	v0.17.8 -> v0.22.1
github.com/grpc-ecosystem/grpc-gateway/v2	v2.20.0 -> v2.25.1
github.com/mailru/easyjson	v0.7.7 -> v0.9.0
github.com/prometheus/client_golang	v1.18.0 -> v1.20.5
github.com/prometheus/common	v0.46.0 -> v0.61.0
go.etcd.io/etcd/api/v3	v3.5.16 -> v3.5.17
go.etcd.io/etcd/client/pkg/v3	v3.5.16 -> v3.5.17
go.etcd.io/etcd/client/v3	v3.5.16 -> v3.5.17
go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc	v0.51.0 -> v0.58.0
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp	v0.51.0 -> v0.58.0
go.opentelemetry.io/otel	v1.26.0 -> v1.33.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace	v1.26.0 -> v1.33.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc	v1.26.0 -> v1.33.0
go.opentelemetry.io/otel/metric	v1.26.0 -> v1.33.0
go.opentelemetry.io/otel/sdk	v1.26.0 -> v1.33.0
go.opentelemetry.io/otel/trace	v1.26.0 -> v1.33.0
go.opentelemetry.io/proto/otlp	v1.2.0 -> v1.4.0
golang.org/x/crypto	v0.27.0 -> v0.31.0
golang.org/x/mod	v0.21.0 -> v0.22.0
golang.org/x/net	v0.29.0 -> v0.33.0
golang.org/x/oauth2	v0.21.0 -> v0.24.0
golang.org/x/sync	v0.8.0 -> v0.10.0
golang.org/x/sys	v0.25.0 -> v0.28.0
golang.org/x/term	v0.24.0 -> v0.27.0
golang.org/x/text	v0.18.0 -> v0.21.0
golang.org/x/time	v0.5.0 -> v0.8.0
golang.org/x/tools	v0.25.0 -> v0.28.0
google.golang.org/genproto/googleapis/api	v0.0.0-20240903143218-8af14fe29dc1 -> v0.0.0-20241219192143-6b3ec007d9bb
google.golang.org/genproto/googleapis/rpc	v0.0.0-20240903143218-8af14fe29dc1 -> v0.0.0-20241219192143-6b3ec007d9bb
google.golang.org/grpc	v1.66.2 -> v1.69.2
google.golang.org/protobuf	v1.34.2 -> v1.36.0
k8s.io/api	v0.30.5 -> v0.32.0
k8s.io/apimachinery	v0.30.5 -> v0.32.0
k8s.io/apiserver	v0.30.5 -> v0.32.0
k8s.io/component-base	v0.30.5 -> v0.32.0
k8s.io/kms	v0.30.5 -> v0.32.0
k8s.io/kube-openapi	v0.0.0-20240903163716-9e1beecbcb38 -> v0.0.0-20241212222426-2c72e554b1e7
k8s.io/utils	v0.0.0-20240902221715-702e33fdd3c3 -> v0.0.0-20241210054802-24370beab758
sigs.k8s.io/apiserver-network-proxy/konnectivity-client	v0.30.3 -> v0.31.1
sigs.k8s.io/controller-runtime	v0.18.5 -> v0.19.0
sigs.k8s.io/json	v0.0.0-20221116044647-bc3834ca7abd -> v0.0.0-20241014173422-cfa47c3a1cc8
sigs.k8s.io/structured-merge-diff/v4	v4.4.1 -> v4.5.0