Commit d13b252
committed
chore(deps): update helm charts (#13)
This PR contains the following updates:
| Package | Update | Change |
|---|---|---|
| [cert-manager](https://cert-manager.io) ([source](https://github.com/cert-manager/cert-manager)) | minor | `v1.19.x` → `1.21.x` |
| [longhorn](https://github.com/longhorn/longhorn) ([source](https://github.com/longhorn/charts)) | minor | `v1.11.1` → `1.12.0` |
| [nvidia-device-plugin](https://github.com/NVIDIA/k8s-device-plugin) | minor | `0.17.0` → `0.19.3` |
---
### Release Notes
<details>
<summary>cert-manager/cert-manager (cert-manager)</summary>
### [`v1.21.1`](https://github.com/cert-manager/cert-manager/releases/tag/v1.21.1)
[Compare Source](https://github.com/cert-manager/cert-manager/compare/v1.21.0...v1.21.1)
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
v1.21.1 fixes a controller panic for Certificates with `spec.renewal.policy: Disabled`, a regression in 1.21.0 which caused log spam and dropped Secret informer events, Issuers and ClusterIssuers getting stuck at `Ready=False` (`InvalidSolver`) when a referenced ACME DNS-01 solver Secret is created after the Issuer, and the commented Gateway API example in the Helm chart values. It also updates several dependencies to fix reported security vulnerabilities.
All users should upgrade.
#### Changes by Kind
##### Bug or Regression
- Avoid controller panic if a Certificate sets spec.renewal.policy=Disabled ([#​9038](https://github.com/cert-manager/cert-manager/issues/9038), [@​sklirg](https://github.com/sklirg))
- Fix Issuer/ClusterIssuer stuck at Ready=False/InvalidSolver after a missing ACME DNS-01 solver Secret is created ([#​9083](https://github.com/cert-manager/cert-manager/issues/9083), [@​SebTardif](https://github.com/SebTardif))
- Fix log spam and dropped Secret informer events for non-cert-manager Secrets, caused by a generics regression introduced in 1.21.0. ([#​9037](https://github.com/cert-manager/cert-manager/issues/9037), [@​wallrj-cyberark](https://github.com/wallrj-cyberark))
- Fixed the commented Gateway API config example in the Helm chart values to use `gatewayAPI.enabled` instead of the invalid `gatewayAPI.enable`. ([#​9012](https://github.com/cert-manager/cert-manager/issues/9012), [@​mateenali66](https://github.com/mateenali66))
##### Other (Cleanup or Flake)
- Bump `golang.org/x/text` to v0.40.0 to fix a reported security vulnerability ([#​9039](https://github.com/cert-manager/cert-manager/issues/9039), [@​wallrj-cyberark](https://github.com/wallrj-cyberark))
- Bump `google.golang.org/grpc` to v1.82.1 to fix a reported security vulnerability ([#​9063](https://github.com/cert-manager/cert-manager/issues/9063))
- Bump `github.com/google/cel-go` to v0.29.0 to fix a reported security vulnerability ([#​9072](https://github.com/cert-manager/cert-manager/issues/9072))
- Bump `go.opentelemetry.io/otel` to v1.44.0 to fix a reported security vulnerability ([#​9073](https://github.com/cert-manager/cert-manager/issues/9073))
- Update distroless base images ([#​9000](https://github.com/cert-manager/cert-manager/issues/9000), [#​9025](https://github.com/cert-manager/cert-manager/issues/9025))
### [`v1.21.0`](https://github.com/cert-manager/cert-manager/releases/tag/v1.21.0)
[Compare Source](https://github.com/cert-manager/cert-manager/compare/v1.20.3...v1.21.0)
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
cert-manager 1.21 brings ACME Renewal Information (ARI) support, AWS IAM authentication for the Vault issuer, several security hardening changes, and continued improvements to Gateway API integration and cainjector. There are three breaking changes related to Helm chart RBAC and metrics values — review them carefully before upgrading.
#### Known Issues
- **Controller crash-loops when a Certificate sets `renewal.policy: Disabled`**: the new Certificate renewal policies feature ([#​8258](https://github.com/cert-manager/cert-manager/issues/8258)) causes a nil pointer dereference panic in the trigger controller whenever a Certificate's `spec.renewal.policy` is set to `Disabled` — `pki.RenewalTime()` returns `(nil, nil)` for that policy, but the caller unconditionally dereferences the result. This crashes the controller process (crash-loop) for any cluster with such a Certificate. **Workaround**: do not set `renewal.policy: Disabled` on any Certificate until this is fixed; remove the field (or set a different policy) from any Certificate that already has it, and restart the controller if it is currently crash-looping. See [#​9031](https://github.com/cert-manager/cert-manager/issues/9031) for details.
- **Log spam for non-cert-manager-labelled Secret events**: the typed predicates refactoring ([#​8407](https://github.com/cert-manager/cert-manager/issues/8407)) causes `filteredEventHandler` type assertion failures (`"OnAdd missing Object"`, `"OnUpdate missing ObjectOld"`, `"OnDelete missing Object"`) for every non-cert-manager-labelled Secret event, multiplied by 7 certificate sub-controllers. **This is cosmetic only** — the affected controllers only need events from cert-manager-labelled Secrets (which arrive via the typed informer); the metadata informer events were always filtered out by predicates in previous versions. Issuer and ClusterIssuer controllers are not affected. See [#​8994](https://github.com/cert-manager/cert-manager/issues/8994) for details.
- **Issuer/ClusterIssuer can get stuck at `Ready: False, Reason: InvalidSolver` and never self-correct**: new eager validation of ACME solver Secrets ([#​8255](https://github.com/cert-manager/cert-manager/issues/8255)) means an Issuer/ClusterIssuer referencing a solver Secret (e.g. a DNS01 provider credential) that doesn't exist yet will correctly report `Ready: False`, but creating the missing Secret afterwards does not trigger re-reconciliation — the controller's Secret-watch logic was never updated to recognise solver Secrets. It will only recover on the next 10-hour informer resync, a change to the Issuer/ClusterIssuer's own spec, or a controller restart. **Workaround**: after creating the missing Secret, make a trivial edit to the Issuer/ClusterIssuer spec (or delete and recreate it) to force reconciliation. See [#​9036](https://github.com/cert-manager/cert-manager/issues/9036) for details and a fix proposal.
#### Major Themes
##### Default `tokenrequest` RBAC removed from Helm chart
> ⚠️ Breaking change
The Helm chart no longer creates a default `Role` and `RoleBinding` granting the cert-manager controller permission to create tokens for its own ServiceAccount (`serviceaccounts/token: create`). No documented workflow requires this RBAC — the Route53 docs section that motivated it was removed in 2024.
If you use `serviceAccountRef.name` pointing at the controller ServiceAccount, you must now either create your own `Role`/`RoleBinding` granting `serviceaccounts/token: create`, or migrate to a dedicated ServiceAccount (recommended — see the [Vault](https://cert-manager.io/docs/configuration/vault/) or [Route53](https://cert-manager.io/docs/configuration/acme/dns01/route53/) documentation).
##### Restrict Challenge and Order RBAC in `cert-manager-edit` ClusterRole
> ⚠️ Potentially breaking change
The `cert-manager-edit` aggregate ClusterRole no longer grants `create` for `challenges.acme.cert-manager.io` or `create`, `patch`, `update` for `orders.acme.cert-manager.io` ([`GHSA-8rvj-mm4h-c258`](https://github.com/cert-manager/cert-manager/security/advisories/GHSA-8rvj-mm4h-c258)). These resources are internal to cert-manager's ACME workflow. Challenge `patch` and `update` are retained because users may need them to remove stuck finalizers.
This change was already shipped in v1.20.3 and v1.19.6, so if you are running one of those versions this will not be a breaking change. If you have tooling that creates Challenge or Order resources directly, you will need to grant those permissions explicitly.
##### Metrics port name and path Helm values removed
> ⚠️ Breaking change
The Helm values `prometheus.servicemonitor.targetPort`, `prometheus.servicemonitor.path`, and `prometheus.podmonitor.path` have been removed. The controller Service metrics port has been renamed from `tcp-prometheus-servicemonitor` to `http-metrics`. Because the Helm values schema uses `additionalProperties: false`, users who still have any of the removed keys in their values overrides will see a schema validation error on upgrade — remove them before upgrading. ([#​8952](https://github.com/cert-manager/cert-manager/issues/8952))
##### ACME and Certificate Management
- **ACME Renewal Information (ARI)**: experimental support for [RFC 9773](https://www.rfc-editor.org/rfc/rfc9773) behind the `ACMEUseARI` feature gate. When enabled, cert-manager queries the ACME server's `renewalInfo` endpoint for the recommended renewal window, allowing servers like Let's Encrypt to proactively prompt renewal during mass revocations or CA key rollovers. ([#​8798](https://github.com/cert-manager/cert-manager/issues/8798))
- **`waitInsteadOfSelfCheck` solver option**: skip cert-manager's own self-check and instead wait a configured duration before asking the ACME server to validate. An escape hatch for split-horizon DNS and NAT hairpin environments. See [configuration details](https://cert-manager.io/docs/configuration/acme/#skip-the-self-check-with-waitinsteadofselfcheck). ([#​8858](https://github.com/cert-manager/cert-manager/issues/8858))
- **AWS IAM authentication for Vault**: the Vault issuer now supports IRSA, EKS Pod Identity, and ambient EC2/ECS credentials, removing the need for long-lived AWS Secrets. ([#​8422](https://github.com/cert-manager/cert-manager/issues/8422))
- **Certificate renewal policies**: a new `renewalPolicies` field on the Certificate API provides more expressive control over renewal scheduling, complementing `renewBefore` and `renewBeforePercentage`. ([#​8258](https://github.com/cert-manager/cert-manager/issues/8258))
- **Configurable CertificateRequest retry backoff**: the new `--certificate-request-maximum-backoff-duration` flag (default: 32 hours) caps the exponential backoff for failed CertificateRequests, useful for environments with scheduled CA maintenance windows. ([#​8893](https://github.com/cert-manager/cert-manager/issues/8893))
- **Modern2026 [PKCS#12](https://github.com/PKCS/cert-manager/issues/12) profile**: a new FIPS 140-3 compatible encoding profile using AES-256 + SHA-256 KDFs instead of legacy 3DES/RC2. ([#​8841](https://github.com/cert-manager/cert-manager/issues/8841))
- **Webhook certificate renewal after system suspend**: the webhook now detects missed certificate renewals after system suspend (S3/S4) or VM live migration by polling wall-clock time, recovering within one minute of resume. ([#​8464](https://github.com/cert-manager/cert-manager/issues/8464))
##### Gateway API and cainjector
- **HTTP01 ListenerSet parentRef fallback**: the `acme.cert-manager.io/http01-parentreffallback: "true"` annotation causes cert-manager to use the parent Gateway for solver HTTPRoutes instead of the ListenerSet, enabling TLS-only ListenerSets to use a shared HTTP listener for ACME challenges. ([#​8749](https://github.com/cert-manager/cert-manager/issues/8749))
- **`cert-manager.io/ignore-tls-listeners` annotation**: exclude specific Gateway TLS listeners from certificate management. ([#​8727](https://github.com/cert-manager/cert-manager/issues/8727))
- **Additional listener protocols**: configurable listener protocols beyond the default set. ([#​8683](https://github.com/cert-manager/cert-manager/issues/8683))
- **`enableGatewayAPI` configuration restructure**: `enableGatewayAPI` and `enableGatewayAPIListenerSet` are deprecated in favor of `gatewayAPI.enabled` / `gatewayAPI.enableListenerSet`. The old fields continue to work. ([#​8732](https://github.com/cert-manager/cert-manager/issues/8732))
- **`CAInjectorMerging` promoted to GA**: unconditionally enabled; will be removed in a future release. ([#​8583](https://github.com/cert-manager/cert-manager/issues/8583))
- **cainjector server-side apply unconditional**: the `ServerSideApply` feature gate is deprecated. ([#​8692](https://github.com/cert-manager/cert-manager/issues/8692))
- **cainjector `--ignore-namespaces` flag**: skip specified namespaces when watching Secrets for injection. ([#​8614](https://github.com/cert-manager/cert-manager/issues/8614))
##### Deployment and Observability
- **Venafi OAuth token observability**: a new `AuthFailed` Issuer condition reason distinguishes bad credentials from transient errors. PANW NGTS is now supported as a Venafi backend. ([#​8808](https://github.com/cert-manager/cert-manager/issues/8808), [#​8779](https://github.com/cert-manager/cert-manager/issues/8779))
- **`runtimeClassName` support**: configurable for cert-manager components and ACME HTTP01 solver pods. ([#​8791](https://github.com/cert-manager/cert-manager/issues/8791), [#​8976](https://github.com/cert-manager/cert-manager/issues/8976))
- **`startupapicheck.ttlSecondsAfterFinished`**: opt-in automatic cleanup of the startupapicheck Job. ([#​8523](https://github.com/cert-manager/cert-manager/issues/8523))
- **`--acme-http01-solver-extra-labels`**: propagate `global.commonLabels` to dynamically-created ACME HTTP01 solver resources. ([#​8761](https://github.com/cert-manager/cert-manager/issues/8761))
##### Notable Bug Fixes
- **Integer overflow in `renewBeforePercentage`**: Certificates with durations longer than approximately 3 years were incorrectly rejected or assigned incorrect renewal times. ([#​8947](https://github.com/cert-manager/cert-manager/issues/8947))
- **Infinite re-issuance loop**: cert-manager no longer loops when an issuer returns an already-expired certificate. ([#​8610](https://github.com/cert-manager/cert-manager/issues/8610))
- **ACME transient network errors**: challenges no longer permanently fail on TLS handshake timeouts, DNS resolution failures, or context cancellation during nonce fetches and authorization waits. ([#​8760](https://github.com/cert-manager/cert-manager/issues/8760))
- **DNS-over-HTTPS response body cap**: response body reads are now bounded at 128 KB to prevent potential OOM. ([#​8803](https://github.com/cert-manager/cert-manager/issues/8803))
- **Vault path traversal**: the Vault issuer webhook now rejects `..` path segments, preventing `path.Join` from silently resolving relative segments. ([#​8930](https://github.com/cert-manager/cert-manager/issues/8930))
- **DNS issuer secrets validated before ready**: prevents silent misconfiguration. ([#​8255](https://github.com/cert-manager/cert-manager/issues/8255))
#### 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:
- [@​Copilot](https://github.com/Copilot)
- [@​FelixPhipps](https://github.com/FelixPhipps)
- [@​Peac36](https://github.com/Peac36)
- [@​SebTardif](https://github.com/SebTardif)
- [@​apkatsikas](https://github.com/apkatsikas)
- [@​bitloi](https://github.com/bitloi)
- [@​dap0am](https://github.com/dap0am)
- [@​figaw](https://github.com/figaw)
- [@​immanuwell](https://github.com/immanuwell)
- [@​jabbrwcky](https://github.com/jabbrwcky)
- [@​jnohlgard](https://github.com/jnohlgard)
- [@​jsoref](https://github.com/jsoref)
- [@​ltwongaa](https://github.com/ltwongaa)
- [@​lunarwhite](https://github.com/lunarwhite)
- [@​mateenali66](https://github.com/mateenali66)
- [@​onurmicoogullari](https://github.com/onurmicoogullari)
- [@​putongyong](https://github.com/putongyong)
- [@​seanorama](https://github.com/seanorama)
- [@​texasich](https://github.com/texasich)
for their contributions, comments and support!
Also, thanks to the cert-manager maintainer team for their help in this release:
- [@​SgtCoDFish](https://github.com/SgtCoDFish)
- [@​ThatsMrTalbot](https://github.com/ThatsMrTalbot)
- [@​erikgb](https://github.com/erikgb)
- [@​hjoshi123](https://github.com/hjoshi123)
- [@​inteon](https://github.com/inteon)
- [@​maelvls](https://github.com/maelvls)
- [@​munnerz](https://github.com/munnerz)
- [@​wallrj](https://github.com/wallrj)
- [@​wallrj-cyberark](https://github.com/wallrj-cyberark)
And finally, thanks to the cert-manager steering committee for their feedback in this release cycle:
- [@​FlorianLiebhart](https://github.com/FlorianLiebhart)
- [@​TrilokGeer](https://github.com/TrilokGeer)
- [@​ianarsenault](https://github.com/ianarsenault)
- [@​ssyno](https://github.com/ssyno)
#### Changes since v1.20.0
##### Feature
- Add Venafi OAuth token request observability and a new `AuthFailed` Issuer condition reason to distinguish bad credentials from transient infrastructure errors. ([#​8808](https://github.com/cert-manager/cert-manager/issues/8808), [@​FelixPhipps](https://github.com/FelixPhipps))
- Add `certificateRequestMaximumBackoffDuration` controller configuration option to cap retry backoff time for failed CertificateRequests. Configurable via config file, `--certificate-request-maximum-backoff-duration` CLI flag, or Helm value `config.certificateRequestMaximumBackoffDuration`. Defaults to 32 hours for backward compatibility. ([#​8893](https://github.com/cert-manager/cert-manager/issues/8893), [@​lunarwhite](https://github.com/lunarwhite))
- Add an optional `waitInsteadOfSelfCheck` field to ACME HTTP01 and DNS01 solvers so cert-manager can skip its own self-check and ask the ACME server to validate after a configured wait. ([#​8858](https://github.com/cert-manager/cert-manager/issues/8858), [@​wallrj](https://github.com/wallrj))
- Add configurable `runtimeClassName` support for cert-manager components and ACME HTTP01 solver pods. ([#​8791](https://github.com/cert-manager/cert-manager/issues/8791), [@​jsoref](https://github.com/jsoref))
- Add direct configurable `runtimeClassName` support for ACME HTTP01 solver pods via the `acmesolver.runtimeClassName` Helm value. ([#​8976](https://github.com/cert-manager/cert-manager/issues/8976), [@​erikgb](https://github.com/erikgb))
- Add new controller flag `--acme-http01-solver-extra-labels`, allowing Helm's `global.commonLabels` to propagate to all dynamically-created ACME HTTP01 solver resources (Pods, Services, Ingresses, or Gateway API HTTPRoutes). ([#​8761](https://github.com/cert-manager/cert-manager/issues/8761), [@​lunarwhite](https://github.com/lunarwhite))
- Add opt-in `startupapicheck.ttlSecondsAfterFinished` Helm value to enable automatic cleanup of the startupapicheck Job via the Kubernetes TTL-after-finished controller. ([#​8523](https://github.com/cert-manager/cert-manager/issues/8523), [@​dap0am](https://github.com/dap0am))
- Added ARI support through the ACMEUseARI feature gate. ([#​8798](https://github.com/cert-manager/cert-manager/issues/8798), [@​hjoshi123](https://github.com/hjoshi123))
- Added AWS IAM authentication support for Vault issuer, including IRSA (IAM Roles for Service Accounts) and ambient credentials (EC2/ECS). ([#​8422](https://github.com/cert-manager/cert-manager/issues/8422), [@​bitloi](https://github.com/bitloi))
- Added `cert-manager.io/ignore-tls-listeners` annotation for ignoring gwapi listeners. ([#​8727](https://github.com/cert-manager/cert-manager/issues/8727), [@​hjoshi123](https://github.com/hjoshi123))
- Added option to specify additional listener protocols the GatewayAPI integration will consider when creating certificates. ([#​8683](https://github.com/cert-manager/cert-manager/issues/8683), [@​ThatsMrTalbot](https://github.com/ThatsMrTalbot))
- Adds support for the Modern2026 go-pkcs12 profile and FIPS 140-3 ([#​8841](https://github.com/cert-manager/cert-manager/issues/8841), [@​seanorama](https://github.com/seanorama))
- Cainjector: A new flag `--ignore-namespaces` was added to the cainjector binary. It can be used to filter out namespaces from being watched for secrets to use for injectables. ([#​8614](https://github.com/cert-manager/cert-manager/issues/8614), [@​figaw](https://github.com/figaw))
- Disabled client side rate-limiting if AP\&F is enabled. ([#​8757](https://github.com/cert-manager/cert-manager/issues/8757), [@​hjoshi123](https://github.com/hjoshi123))
- Extend the Venafi/CyberArk integration to also support PANW NGTS. ([#​8779](https://github.com/cert-manager/cert-manager/issues/8779), [@​FelixPhipps](https://github.com/FelixPhipps))
- Adding certificate renewal policies ([#​8258](https://github.com/cert-manager/cert-manager/issues/8258), [@​hjoshi123](https://github.com/hjoshi123))
- Make cainjector use SSA unconditionally and deprecate the ServerSideApply feature gate ([#​8692](https://github.com/cert-manager/cert-manager/issues/8692), [@​erikgb](https://github.com/erikgb))
- Processed annotations `cert-manager.io/alt-names`, `cert-manager.io/ip-sans` to Certificates generated from ingress like objects in cert-shim controllers. ([#​8927](https://github.com/cert-manager/cert-manager/issues/8927), [@​jabbrwcky](https://github.com/jabbrwcky))
- Promote the CAInjectorMerging feature gate to GA ([#​8583](https://github.com/cert-manager/cert-manager/issues/8583), [@​Copilot](https://github.com/Copilot))
- When using ACME HTTP-01 with a ListenerSet, setting the annotation `acme.cert-manager.io/http01-parentreffallback: "true"` causes cert-manager to use the parent Gateway as the solver HTTPRoute parentRef instead of the ListenerSet. This enables TLS-only ListenerSets to rely on a shared Gateway HTTP listener for ACME challenges. ([#​8749](https://github.com/cert-manager/cert-manager/issues/8749), [@​apkatsikas](https://github.com/apkatsikas))
##### Bug or Regression
- **BREAKING**: The Helm chart no longer ships a default `Role` and `RoleBinding` granting the cert-manager controller ServiceAccount permission to create tokens for itself (`serviceaccounts/token: create`). This RBAC was added in v1.16 ([#​7213](https://github.com/cert-manager/cert-manager/issues/7213)) but no documented workflow requires it, and the motivating Route53 docs section was removed in Oct 2024. If you rely on `serviceAccountRef.name` pointing at the controller ServiceAccount (an undocumented pattern), you must now create your own `Role` and `RoleBinding` granting `serviceaccounts/token: create` on that ServiceAccount, or migrate to one of the documented patterns (IRSA ambient, or a dedicated ServiceAccount with its own RBAC). ([#​8931](https://github.com/cert-manager/cert-manager/issues/8931), [@​wallrj-cyberark](https://github.com/wallrj-cyberark))
- ACME challenges no longer terminally fail on transient network errors (TLS handshake timeouts, DNS failures, context cancellation) during nonce fetches and authorization waits. The challenge controller returns the error and lets the workqueue retry with backoff. ([#​8760](https://github.com/cert-manager/cert-manager/issues/8760), [@​texasich](https://github.com/texasich))
- Add dns issuer secrets validation before marking it as ready ([#​8255](https://github.com/cert-manager/cert-manager/issues/8255), [@​Peac36](https://github.com/Peac36))
- Add missing issuer finalizer RBAC to the order controller to support owner references ([#​8654](https://github.com/cert-manager/cert-manager/issues/8654), [@​erikgb](https://github.com/erikgb))
- ClusterIssuer metrics collector now correctly respects the enabled-controllers configuration, avoiding a redundant startup when only operating within a namespace. ([#​8822](https://github.com/cert-manager/cert-manager/issues/8822), [@​lunarwhite](https://github.com/lunarwhite))
- Fix Venafi TPP issuer setup and signing regression on master: restore authentication of the vcert connector in the client constructor, which was removed in [#​8808](https://github.com/cert-manager/cert-manager/issues/8808). ([#​8843](https://github.com/cert-manager/cert-manager/issues/8843), [@​wallrj-cyberark](https://github.com/wallrj-cyberark))
- Fix a performance issue in the certificateRequestApproval webhook where CertificateRequests referencing a GroupKind whose CRD is not yet installed would trigger repeated API server discovery queries on every admission request. Negative results are now cached for 30 seconds. ([#​8651](https://github.com/cert-manager/cert-manager/issues/8651), [@​mateenali66](https://github.com/mateenali66))
- Fix webhook serving certificate not being renewed after system suspend. ([#​8464](https://github.com/cert-manager/cert-manager/issues/8464), [@​Peac36](https://github.com/Peac36))
- Fixed a rare panic in the trigger controller when a Certificate is deleted from the informer cache while a reconcile is in progress (e.g. during namespace teardown). ([#​8962](https://github.com/cert-manager/cert-manager/issues/8962), [@​hjoshi123](https://github.com/hjoshi123))
- Fixed an integer overflow in `renewBeforePercentage` calculations that caused Certificates with durations longer than approximately 3 years to be incorrectly rejected by validation or assigned incorrect renewal times. ([#​8947](https://github.com/cert-manager/cert-manager/issues/8947), [@​ThatsMrTalbot](https://github.com/ThatsMrTalbot))
- Fixed duplicate `parentRef` bug when both issuer config and annotations are present. ([#​8619](https://github.com/cert-manager/cert-manager/issues/8619), [@​hjoshi123](https://github.com/hjoshi123))
- Fixed infinite re-issuance loop when issuer returns an already expired certificate ([#​8610](https://github.com/cert-manager/cert-manager/issues/8610), [@​onurmicoogullari](https://github.com/onurmicoogullari))
- Fixed local `e2e-setup-samplewebhook` installation to use the samplewebhook image repository and tag from the saved image tarball manifest. ([#​8821](https://github.com/cert-manager/cert-manager/issues/8821), [@​wallrj](https://github.com/wallrj))
- Fixed potential OOM in DNS-over-HTTPS client by bounding response body read with io.LimitReader (128 KB cap). ([#​8803](https://github.com/cert-manager/cert-manager/issues/8803), [@​SebTardif](https://github.com/SebTardif))
- Fixed validation of timezone-prefixed renewal window cron specs without a schedule. ([#​8813](https://github.com/cert-manager/cert-manager/issues/8813), [@​immanuwell](https://github.com/immanuwell))
- Helm chart bugfix: rename image helper to avoid umbrella chart conflicts ([#​8753](https://github.com/cert-manager/cert-manager/issues/8753), [@​FelixPhipps](https://github.com/FelixPhipps))
- Helm: Fix invalid YAML generated when both `webhook.config` and `webhook.volumes` are defined. ([#​8664](https://github.com/cert-manager/cert-manager/issues/8664), [@​jnohlgard](https://github.com/jnohlgard))
- Remove ACME Challenge `create` and Order `create`/`patch`/`update` from the cert-manager-edit aggregate ClusterRole to prevent direct manipulation of these internal resources (GHSA-8rvj-mm4h-c258). ([#​8958](https://github.com/cert-manager/cert-manager/issues/8958), [@​wallrj-cyberark](https://github.com/wallrj-cyberark))
- Remove issuer owner reference from challenges blocking challenge garbage collection ([#​8743](https://github.com/cert-manager/cert-manager/issues/8743), [@​erikgb](https://github.com/erikgb))
- Update logic to identify and preserve the secret matching nextPrivateKeySecretName ([#​8577](https://github.com/cert-manager/cert-manager/issues/8577), [@​putongyong](https://github.com/putongyong))
- Vault Issuer webhook validation now rejects `..` path segments in `spec.vault.path` and auth mount path fields, preventing `path.Join` from silently resolving relative segments before constructing the Vault API request. ([#​8930](https://github.com/cert-manager/cert-manager/issues/8930), [@​wallrj-cyberark](https://github.com/wallrj-cyberark))
##### Other (Cleanup or Flake)
- API cleanup: removed deprecated ObjectReference ([#​8625](https://github.com/cert-manager/cert-manager/issues/8625), [@​inteon](https://github.com/inteon))
- Remove Helm values `prometheus.servicemonitor.targetPort`, `prometheus.servicemonitor.path`, and `prometheus.podmonitor.path`. The metrics path is always `/metrics` and the target port is always `http-metrics`. Rename the controller service metrics port from `tcp-prometheus-servicemonitor` to `http-metrics` for consistency with other workloads. Users must remove these keys from their value overrides before upgrading. ([#​8952](https://github.com/cert-manager/cert-manager/issues/8952), [@​erikgb](https://github.com/erikgb))
- The `enableGatewayAPI` and `enableGatewayAPIListenerSet` fields on `ControllerConfiguration` are deprecated and moved into the `gatewayAPI` sub-struct as `gatewayAPI.enabled` and `gatewayAPI.enableListenerSet`. The old fields continue to work. ([#​8732](https://github.com/cert-manager/cert-manager/issues/8732), [@​ThatsMrTalbot](https://github.com/ThatsMrTalbot))
- Update base images to Debian 13 ([#​8849](https://github.com/cert-manager/cert-manager/issues/8849), [@​ltwongaa](https://github.com/ltwongaa))
### [`v1.20.3`](https://github.com/cert-manager/cert-manager/releases/tag/v1.20.3)
[Compare Source](https://github.com/cert-manager/cert-manager/compare/v1.20.2...v1.20.3)
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
This patch release fixes a security issue ([`GHSA-8rvj-mm4h-c258`](https://github.com/cert-manager/cert-manager/security/advisories/GHSA-8rvj-mm4h-c258), HIGH) where the default `cert-manager-edit` aggregate ClusterRole granted namespace users permission to create ACME `Challenge` and `Order` resources directly. A user who could create a `Challenge` referencing a `ClusterIssuer` could supply attacker-controlled solver configuration while cert-manager loaded credentials from the `ClusterIssuer`'s namespace, bypassing Issuer solver selectors (`dnsZones`, `dnsNames`, `matchLabels`). With the acme-dns provider specifically, this could disclose DNS credentials to an attacker-controlled endpoint.
This release also removes the issuer owner reference from Challenges which was blocking Challenge garbage collection, and updates Go to fix reported CVEs.
All users should upgrade.
> \[!WARNING]
> **Potentially breaking change:** The `cert-manager-edit` aggregate ClusterRole no longer grants `create` for `challenges.acme.cert-manager.io` or `create`, `patch`, `update` for `orders.acme.cert-manager.io`. These resources are internal to cert-manager's ACME workflow and are not intended to be created or modified directly by users. If you have tooling or workflows that create Challenge or Order resources directly (outside of the normal Certificate → CertificateRequest → Order → Challenge flow), you will need to grant those permissions explicitly.
#### Changes by Kind
##### Bug or Regression
- Security (HIGH): Remove Challenge `create` and Order `create`, `patch`, `update` verbs from the `cert-manager-edit` aggregate ClusterRole ([`GHSA-8rvj-mm4h-c258`](https://github.com/cert-manager/cert-manager/security/advisories/GHSA-8rvj-mm4h-c258)). ([#​8940](https://github.com/cert-manager/cert-manager/issues/8940), [@​wallrj-cyberark](https://github.com/wallrj-cyberark))
- Remove issuer owner reference from challenges blocking challenge garbage collection ([#​8759](https://github.com/cert-manager/cert-manager/issues/8759), [@​cert-manager-bot](https://github.com/cert-manager-bot))
##### Other (Cleanup or Flake)
- Bump go to 1.26.3, other deps to fix several govulncheck issues ([#​8789](https://github.com/cert-manager/cert-manager/issues/8789), [@​SgtCoDFish](https://github.com/SgtCoDFish))
- Update Go to `v1.26.4` to fix CVE-2026-27145, CVE-2026-42504, and CVE-2026-42507 ([#​8926](https://github.com/cert-manager/cert-manager/issues/8926), [@​wallrj-cyberark](https://github.com/wallrj-cyberark))
### [`v1.20.2`](https://github.com/cert-manager/cert-manager/releases/tag/v1.20.2)
[Compare Source](https://github.com/cert-manager/cert-manager/compare/v1.20.1...v1.20.2)
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
v1.20.2 fixes invalid YAML generated in the Helm chart when both `webhook.config`
and `webhook.volumes` are defined, and bumps Go to 1.26.2 along with dependencies
to address reported vulnerabilities.
#### Changes by Kind
##### Bug or Regression
- Helm: Fix invalid YAML generated when both `webhook.config` and `webhook.volumes` are defined. ([#​8665](https://github.com/cert-manager/cert-manager/issues/8665), [@​cert-manager-bot](https://github.com/cert-manager-bot))
##### Other (Cleanup or Flake)
- Bump go dependencies with reported vulnerabilities ([#​8704](https://github.com/cert-manager/cert-manager/issues/8704), [@​erikgb](https://github.com/erikgb))
- Bump go to 1.26.2 ([#​8703](https://github.com/cert-manager/cert-manager/issues/8703), [@​erikgb](https://github.com/erikgb))
### [`v1.20.1`](https://github.com/cert-manager/cert-manager/releases/tag/v1.20.1)
[Compare Source](https://github.com/cert-manager/cert-manager/compare/v1.20.0...v1.20.1)
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
v1.20.1 fixes an issue for OpenShift users that has to do with the finalizer RBAC, bumps gRPC to address a reported non-affecting vulnerability, and fixes a duplicate `parentRef` bug when both issuer config and annotations are present (Gateway API).
##### Bug or Regression
- Fixed duplicate `parentRef` bug when both issuer config and annotations are present. ([#​8658](https://github.com/cert-manager/cert-manager/issues/8658), [@​hjoshi123](https://github.com/hjoshi123))
- Add missing issuer finalizer RBAC to the order controller to support owner references. This was preventing OpenShift users from being able to upgrade to v1.20.0. ([#​8655](https://github.com/cert-manager/cert-manager/issues/8655), [@​erikgb](https://github.com/erikgb))
- Bump google.golang.org/grpc to fix vulnerability reported by scanners. This isn't a vulnerability that affects cert-manager, but we are bumping it because it is reported by scanners. ([#​8657](https://github.com/cert-manager/cert-manager/issues/8657), [@​erikgb](https://github.com/erikgb))
### [`v1.20.0`](https://github.com/cert-manager/cert-manager/releases/tag/v1.20.0)
[Compare Source](https://github.com/cert-manager/cert-manager/compare/v1.19.6...v1.20.0)
cert-manager is the easiest way to automatically manage certificates in Kubernetes and OpenShift clusters.
v1.20.0 adds alpha support for the new ListenerSet resource, adds support for Azure Private DNS; parentRefs are no longer required when using ACME with Gateway API, and OtherNames was promoted to Beta.
#### Changes by Kind
##### Feature
- Added a set of flags to permit setting NetworkPolicy across all deployed containers. Remove redundant global IP ranges from example policies. ([#​8370](https://github.com/cert-manager/cert-manager/issues/8370), [@​jcpunk](https://github.com/jcpunk))
- Added selectable fields to custom resource definitions for .spec.issuerRef.{group, kind, name} ([#​8256](https://github.com/cert-manager/cert-manager/issues/8256), [@​tareksha](https://github.com/tareksha))
- Added support for specifying `imagePullSecrets` in the `startupapicheck-job` Helm template to enable pulling images from private registries. ([#​8186](https://github.com/cert-manager/cert-manager/issues/8186), [@​mathieu-clnk](https://github.com/mathieu-clnk))
- Added 'extraContainers' helm chart value, allowing the deployment of arbitrary sidecar containers within the cert-manager operator pod. This can be used to support, for e.g., AWS IAM Roles Anywhere for Route53 DNS01 verification. ([#​8355](https://github.com/cert-manager/cert-manager/issues/8355), [@​dancmeyers](https://github.com/dancmeyers))
- Added `parentRef` override annotations on the Certificate resource. ([#​8518](https://github.com/cert-manager/cert-manager/issues/8518), [@​hjoshi123](https://github.com/hjoshi123))
- Added support for azure private zones for dns01 issuer. ([#​8494](https://github.com/cert-manager/cert-manager/issues/8494), [@​hjoshi123](https://github.com/hjoshi123))
- Added support for configuring PEM decoding size limits, allowing operators to handle larger certificates and keys. ([#​7642](https://github.com/cert-manager/cert-manager/issues/7642), [@​robertlestak](https://github.com/robertlestak))
- Added support for unhealthyPodEvictionPolicy in PodDisruptionBudget ([#​7728](https://github.com/cert-manager/cert-manager/issues/7728), [@​jcpunk](https://github.com/jcpunk))
- For Venafi provider, read `venafi.cert-manager.io/custom-fields` annotation on Issuer/ClusterIssuer and use it as base with override/append capabilities on Certificate level. ([#​8301](https://github.com/cert-manager/cert-manager/issues/8301), [@​k0da](https://github.com/k0da))
- Improve error message when CA issuers are misconfigured to use a clashing secret name ([#​8374](https://github.com/cert-manager/cert-manager/issues/8374), [@​majiayu000](https://github.com/majiayu000))
- Introduce a new Ingress annotation `acme.cert-manager.io/http01-ingress-ingressclassname` to override `http01.ingress.ingressClassName` field in HTTP-01 challenge solvers. ([#​8244](https://github.com/cert-manager/cert-manager/issues/8244), [@​lunarwhite](https://github.com/lunarwhite))
- Update `global.nodeSelector` to helm chart to perform a `merge` and allow for a single `nodeSelector` to be set across all services. ([#​8195](https://github.com/cert-manager/cert-manager/issues/8195), [@​StingRayZA](https://github.com/StingRayZA))
- Vault issuers will now include the Vault server address as one of the default audiences on generated service account tokens. ([#​8228](https://github.com/cert-manager/cert-manager/issues/8228), [@​terinjokes](https://github.com/terinjokes))
- Added experimental `XListenerSets` feature gate ([#​8394](https://github.com/cert-manager/cert-manager/issues/8394), [@​hjoshi123](https://github.com/hjoshi123))
##### Documentation
- Add GWAPI documentation to NOTES.TXT in helm chart ([#​8353](https://github.com/cert-manager/cert-manager/issues/8353), [@​jaxels10](https://github.com/jaxels10))
##### Bug or Regression
- Adds logs for cases when acme server returns us a fatal error in the order controller ([#​8199](https://github.com/cert-manager/cert-manager/issues/8199), [@​Peac36](https://github.com/Peac36))
- Fixed an issue where kind or group in the issuerRef of a Certificate was omitted, upgrading to 1.19.x incorrectly caused the certificate to be renewed ([#​8160](https://github.com/cert-manager/cert-manager/issues/8160), [@​inteon](https://github.com/inteon))
- Changes to the Duration and RenewBefore annotations on ingress and gateway-api resources will now trigger certificate updates. ([#​8232](https://github.com/cert-manager/cert-manager/issues/8232), [@​eleanor-merry](https://github.com/eleanor-merry))
- Fix an issue where ACME challenge TXT records are not cleaned up when there are many resource records in CloudDNS. ([#​8456](https://github.com/cert-manager/cert-manager/issues/8456), [@​tkna](https://github.com/tkna))
- Fix unregulated retries with the DigitalOcean DNS-01 solver
Add full detailed DNS-01 errors to the events attached to the Challenge, for easier debugging ([#​8221](https://github.com/cert-manager/cert-manager/issues/8221), [@​wallrj-cyberark](https://github.com/wallrj-cyberark))
- Fixed an infinite re-issuance loop that could occur when an issuer returns a certificate with a public key that doesn't match the CSR. The issuing controller now validates the certificate before storing it and fails with backoff on mismatch. ([#​8403](https://github.com/cert-manager/cert-manager/issues/8403), [@​calm329](https://github.com/calm329))
- Fixed an issue where HTTP-01 challenges failed when the Host header contains an IPv6 address. This means that users can now issue IP address certificates for IPv6 address subjects. ([#​8424](https://github.com/cert-manager/cert-manager/issues/8424), [@​SlashNephy](https://github.com/SlashNephy))
- Fixed the HTTP-01 Gateway solver creating invalid HTTPRoutes by not setting spec.hostnames when the challenge DNSName is an IP address. ([#​8443](https://github.com/cert-manager/cert-manager/issues/8443), [@​alviss7](https://github.com/alviss7))
- Revert API defaults for issuer reference kind and group introduced in 0.19.0 ([#​8173](https://github.com/cert-manager/cert-manager/issues/8173), [@​erikgb](https://github.com/erikgb))
- Security (MODERATE): Fix a potential panic in the cert-manager controller when a DNS response in an unexpected order was cached. If an attacker was able to modify DNS responses (or if they controlled the DNS server) it was possible to cause denial of service for the cert-manager controller. ([#​8469](https://github.com/cert-manager/cert-manager/issues/8469), [@​SgtCoDFish](https://github.com/SgtCoDFish))
- Update Go to `v1.25.5` to fix `CVE-2025-61727` and `CVE-2025-61729` ([#​8290](https://github.com/cert-manager/cert-manager/issues/8290), [@​octo-sts](https://github.com/octo-sts)\[bot])
- When Prometheus monitoring is enabled, the metrics label is now set to the intended value of `cert-manager`. Previously, it was set depending on various factors (namespace cert-manager is installed in and/or Helm release name). ([#​8162](https://github.com/cert-manager/cert-manager/issues/8162), [@​LiquidPL](https://github.com/LiquidPL))
##### Other (Cleanup or Flake)
- Promoted the OtherNames feature to Beta and enabled it by default ([#​8288](https://github.com/cert-manager/cert-manager/issues/8288), [@​wallrj-cyberark](https://github.com/wallrj-cyberark))
- Promoting `XListenerSets` feature gate to `ListenerSets` ([#​8501](https://github.com/cert-manager/cert-manager/issues/8501), [@​hjoshi123](https://github.com/hjoshi123))
- Rebranding of the Venafi Issuer to CyberArk ([#​8215](https://github.com/cert-manager/cert-manager/issues/8215), [@​iossifbenbassat123](https://github.com/iossifbenbassat123))
- Switched to SSA for challenge finalizer updates ([#​8519](https://github.com/cert-manager/cert-manager/issues/8519), [@​inteon](https://github.com/inteon))
- The default container user (UID) is now 65532 (previously 1000) and the default container group (GID) is now 65532 (previously 0) ([#​8408](https://github.com/cert-manager/cert-manager/issues/8408), [@​wallrj-cyberark](https://github.com/wallrj-cyberark))
- The feature-gate DefaultPrivateKeyRotationPolicyAlways moved from Beta to GA and can no longer be disabled. ([#​8287](https://github.com/cert-manager/cert-manager/issues/8287), [@​wallrj-cyberark](https://github.com/wallrj-cyberark))
- Update cert-manager's ACME client, forked from golang/x/crypto ([#​8268](https://github.com/cert-manager/cert-manager/issues/8268), [@​SgtCoDFish](https://github.com/SgtCoDFish))
- Use the latest version of Kyverno (1.16.2) in the best-practice installation tests ([#​8389](https://github.com/cert-manager/cert-manager/issues/8389), [@​wallrj-cyberark](https://github.com/wallrj-cyberark))
- We stopped testing with Coutour due to it not supporting the new XListenerSet resource, and moved to kgateway. ([#​8426](https://github.com/cert-manager/cert-manager/issues/8426), [@​hjoshi123](https://github.com/hjoshi123))
</details>
<details>
<summary>longhorn/charts (longhorn)</summary>
### [`v1.12.0`](https://github.com/longhorn/charts/releases/tag/longhorn-1.12.0)
[Compare Source](https://github.com/longhorn/charts/compare/longhorn-1.11.3...longhorn-1.12.0)
Longhorn is a distributed block storage system for Kubernetes.
### [`v1.11.3`](https://github.com/longhorn/charts/releases/tag/longhorn-1.11.3)
[Compare Source](https://github.com/longhorn/charts/compare/longhorn-1.11.2...longhorn-1.11.3)
Longhorn is a distributed block storage system for Kubernetes.
### [`v1.11.2`](https://github.com/longhorn/charts/releases/tag/longhorn-1.11.2)
[Compare Source](https://github.com/longhorn/charts/compare/longhorn-1.11.1...longhorn-1.11.2)
Longhorn is a distributed block storage system for Kubernetes.
</details>
<details>
<summary>NVIDIA/k8s-device-plugin (nvidia-device-plugin)</summary>
### [`v0.19.3`](https://github.com/NVIDIA/k8s-device-plugin/blob/HEAD/CHANGELOG.md#v0193)
[Compare Source](https://github.com/NVIDIA/k8s-device-plugin/compare/v0.19.2...v0.19.3)
- bump nvcr.io/nvidia/distroless/go to v4.0.8-dev ([#​1852](https://github.com/NVIDIA/k8s-device-plugin/issues/1852))
- revert default enablement of features mofed, gdrcopy and mofed ([#​1837](https://github.com/NVIDIA/k8s-device-plugin/issues/1837))
- bump golang version to 1.26.4 ([#​1828](https://github.com/NVIDIA/k8s-device-plugin/issues/1828))
- bump golang.org/x/net to v0.56.0 ([#​1867](https://github.com/NVIDIA/k8s-device-plugin/issues/1867))
### [`v0.19.2`](https://github.com/NVIDIA/k8s-device-plugin/blob/HEAD/CHANGELOG.md#v0192)
[Compare Source](https://github.com/NVIDIA/k8s-device-plugin/compare/v0.19.1...v0.19.2)
- Bump golang version to 1.26.3 ([#​1754](https://github.com/NVIDIA/k8s-device-plugin/issues/1754))
- Bump nvidia/distroless/go to v4.0.6-dev ([#​1806](https://github.com/NVIDIA/k8s-device-plugin/issues/1806))
- Bump nvidia-container-toolkit to v1.19.1 ([#​1798](https://github.com/NVIDIA/k8s-device-plugin/issues/1798))
- Always use a dedicated service account in the helm chart ([#​1804](https://github.com/NVIDIA/k8s-device-plugin/issues/1804))
### [`v0.19.1`](https://github.com/NVIDIA/k8s-device-plugin/blob/HEAD/CHANGELOG.md#v0191)
[Compare Source](https://github.com/NVIDIA/k8s-device-plugin/compare/v0.19.0...v0.19.1)
- wsl: report a single "all" device to kubelet ([#​1699](https://github.com/NVIDIA/k8s-device-plugin/issues/1699))
- Fix CDI spec generation to respect driver root for Tegra CSV files ([#​1701](https://github.com/NVIDIA/k8s-device-plugin/issues/1701))
- Bump golang from 1.26.1 to 1.26.2 ([#​1704](https://github.com/NVIDIA/k8s-device-plugin/issues/1704))
* Bump nvidia/distroless/go from v4.0.3-dev to v4.0.4-dev ([#​1702](https://github.com/NVIDIA/k8s-device-plugin/issues/1702))
* Bump google.golang.org/grpc from 1.79.1 to 1.79.3 ([#​1711](https://github.com/NVIDIA/k8s-device-plugin/issues/1711))
* Bump the k8s.io dependencies to v1.35.4 ([#​1710](https://github.com/NVIDIA/k8s-device-plugin/issues/1710))
### [`v0.19.0`](https://github.com/NVIDIA/k8s-device-plugin/blob/HEAD/CHANGELOG.md#v0190)
[Compare Source](https://github.com/NVIDIA/k8s-device-plugin/compare/v0.18.2...v0.19.0)
- Add --sleep-interval=infinite support to GFD for running as a pod ([#​1603](https://github.com/NVIDIA/k8s-device-plugin/issues/1603))
- Fix image tag in static deployment ([#​1604](https://github.com/NVIDIA/k8s-device-plugin/issues/1604))
- Add ownerReference to NodeFeature CRs for garbage collection ([#​1597](https://github.com/NVIDIA/k8s-device-plugin/issues/1597))
- Change default value for gds, gdrcopy and mofed flags ([#​1550](https://github.com/NVIDIA/k8s-device-plugin/issues/1550))
- Fix healthchecking on old devices ([#​1562](https://github.com/NVIDIA/k8s-device-plugin/issues/1562))
- Enable NodeFeature API by default in GFD ([#​1504](https://github.com/NVIDIA/k8s-device-plugin/issues/1504))
- Build multiarch images on native GitHub runners ([#​1468](https://github.com/NVIDIA/k8s-device-plugin/issues/1468))
### [`v0.18.2`](https://github.com/NVIDIA/k8s-device-plugin/blob/HEAD/CHANGELOG.md#v0182)
[Compare Source](https://github.com/NVIDIA/k8s-device-plugin/compare/v0.18.1...v0.18.2)
- Ensure that cdi.FeatureFlags are passed to CDI library
- Fix race condition in config-manager when label is unset
- Fix nested container use cases by ensuring that IPC sockets are not mounted readonly
- Bump NVIDIA Container Toolkit to v1.18.2
- Bump distroless base image to v3.2.2-dev
### [`v0.18.1`](https://github.com/NVIDIA/k8s-device-plugin/blob/HEAD/CHANGELOG.md#v0181)
[Compare Source](https://github.com/NVIDIA/k8s-device-plugin/compare/v0.18.0...v0.18.1)
- Allow CDI feature flags to be set
- Pass driver root to nvinfo.New in device plugin main
- Bump NVIDIA Container Toolkit to v1.18.1
- Bump distroless base image to v3.2.1-dev
- Bump github.com/opencontainers/selinux from 1.12.0 to 1.13.1 ([#​1506](https://github.com/NVIDIA/k8s-device-plugin/issues/1506))
### [`v0.18.0`](https://github.com/NVIDIA/k8s-device-plugin/blob/HEAD/CHANGELOG.md#v0180)
[Compare Source](https://github.com/NVIDIA/k8s-device-plugin/compare/v0.17.4...v0.18.0)
- Rename getHealthCheckXids and clarify documentation
- Add support for explicitly enabling XIDs in health checks
- Deduplicate requested device IDs
- Check for nil before reading boolean config values
- Make gated modes (GDS, MOFED, GDRCOPY) optional in CDI
- Add support for setting gdrcopyEnabled
- Ignore errors getting device memory using NVML
- Ensure that directory volumes have Directory type
- Switch to plain golang image for builds
- Remove unneeded intermediate container
- Update CI definitions
- Switch to distroless golang image
- Update README.md with RuntimeClass
- Pass a single context throughout the device-plugin method call stack ([#​1284](https://github.com/NVIDIA/k8s-device-plugin/issues/1284))
- Remove internal logger in favour of klog ([#​1277](https://github.com/NVIDIA/k8s-device-plugin/issues/1277))
- Remove FAIL\_ON\_INIT\_ERROR from static examples
- Detect blackwell architecture
- Updated .release:staging to stage device-plugin images in nvstaging
- Use MiB instead of MB for gpu-memory
- Ignore XID error 109
- Update README.md adjust set docker runtime default
- Remove nvidia.com/gpu.imex-domain label
- Fix containerd runc config error when creating a kind cluster
- Use stable nividia-container-toolkit repo when creating a kind cluster
- Switch to context package in go stdlib
- Raise a warning instead of an error if GPU mode labeler fails
- Add ada-lovelace architecture label for compute capability 8.9
- Ensure FAIL\_ON\_INIT\_ERROR boolean env is quoted
- Honor fail-on-init-error when no resources are found
- Enable hostPID in the mps-control-daemon pod ([#​1045](https://github.com/NVIDIA/k8s-device-plugin/issues/1045))
### [`v0.17.4`](https://github.com/NVIDIA/k8s-device-plugin/releases/tag/v0.17.4)
[Compare Source](https://github.com/NVIDIA/k8s-device-plugin/compare/v0.17.3...v0.17.4)
#### What's Changed
- Bump slackapi/slack-github-action from 2.1.0 to 2.1.1 by [@​dependabot](https://github.com/dependabot)\[bot] in [#​1317](https://github.com/NVIDIA/k8s-device-plugin/pull/1317)
- Bump github.com/NVIDIA/go-nvlib from 0.7.2 to 0.7.4 by [@​dependabot](https://github.com/dependabot)\[bot] in [#​1346](https://github.com/NVIDIA/k8s-device-plugin/pull/1346)
- Bump golang from 1.23.11 to 1.23.12 in /deployments/devel by [@​dependabot](https://github.com/dependabot)\[bot] in [#​1355](https://github.com/NVIDIA/k8s-device-plugin/pull/1355)
- Ensure that directory volumes have Directory type by [@​elezar](https://github.com/elezar) in [#​1368](https://github.com/NVIDIA/k8s-device-plugin/pull/1368)
- Bump nvidia/cuda from 12.9.1-base-ubi9 to 13.0.0-base-ubi9 in /deployments/container by [@​dependabot](https://github.com/dependabot)\[bot] in [#​1369](https://github.com/NVIDIA/k8s-device-plugin/pull/1369)
- Ignore errors getting device memory using NVML by [@​elezar](https://github.com/elezar) in [#​1374](https://github.com/NVIDIA/k8s-device-plugin/pull/1374)
- Bump project version to v0.17.4 by [@​cdesiniotis](https://github.com/cdesiniotis) in [#​1402](https://github.com/NVIDIA/k8s-device-plugin/pull/1402)
- \[no-relnote] update ngc publishing logic for release pipelines by [@​cdesiniotis](https://github.com/cdesiniotis) in [#​1406](https://github.com/NVIDIA/k8s-device-plugin/pull/1406)
**Full Changelog**: <https://github.com/NVIDIA/k8s-device-plugin/compare/v0.17.3...v0.17.4>
### [`v0.17.3`](https://github.com/NVIDIA/k8s-device-plugin/releases/tag/v0.17.3)
[Compare Source](https://github.com/NVIDIA/k8s-device-plugin/compare/v0.17.2...v0.17.3)
#### What's Changed
- Bump github.com/NVIDIA/nvidia-container-toolkit from 1.17.6 to 1.17.8 by [@​dependabot](https://github.com/dependabot)\[bot] in [#​1275](https://github.com/NVIDIA/k8s-device-plugin/pull/1275)
- Bump nvidia/cuda from 12.9.0-base-ubi9 to 12.9.1-base-ubi9 in /deployments/container by [@​dependabot](https://github.com/dependabot)\[bot] in [#​1300](https://github.com/NVIDIA/k8s-device-plugin/pull/1300)
- Bump github.com/NVIDIA/go-nvml from 0.12.4-1 to 0.12.9-0 by [@​dependabot](https://github.com/dependabot)\[bot] in [#​1287](https://github.com/NVIDIA/k8s-device-plugin/pull/1287)
- Bump golang from 1.23.9 to 1.23.10 in /deployments/devel by [@​dependabot](https://github.com/dependabot)\[bot] in [#​1283](https://github.com/NVIDIA/k8s-device-plugin/pull/1283)
- Bump golang from 1.23.10 to 1.23.11 in /deployments/devel by [@​dependabot](https://github.com/dependabot)\[bot] in [#​1318](https://github.com/NVIDIA/k8s-device-plugin/pull/1318)
- Bump release v0.17.3 by [@​elezar](https://github.com/elezar) in [#​1326](https://github.com/NVIDIA/k8s-device-plugin/pull/1326)
- Backport: Bump golang.org/x/oauth2 from 0.23.0 to 0.27.0 by [@​cdesiniotis](https://github.com/cdesiniotis) in [#​1328](https://github.com/NVIDIA/k8s-device-plugin/pull/1328)
- Updated .release:staging to stage device-plugin images in nvstaging by [@​elezar](https://github.com/elezar) in [#​1329](https://github.com/NVIDIA/k8s-device-plugin/pull/1329)
**Full Changelog**: <https://github.com/NVIDIA/k8s-device-plugin/compare/v0.17.2...v0.17.3>
### [`v0.17.2`](https://github.com/NVIDIA/k8s-device-plugin/releases/tag/v0.17.2)
[Compare Source](https://github.com/NVIDIA/k8s-device-plugin/compare/v0.17.1...v0.17.2)
#### What's Changed
- Update nvidia.com/gpu.product label to include blackwell architectures
- Update documentation to indicate that nvidia.com/gpu.memory label is in MiB instead of MB
**Full Changelog**: <https://github.com/NVIDIA/k8s-device-plugin/compare/v0.17.1...v0.17.2>
### [`v0.17.1`](https://github.com/NVIDIA/k8s-device-plugin/blob/HEAD/CHANGELOG.md#Version-v0171)
[Compare Source](https://github.com/NVIDIA/k8s-device-plugin/compare/v0.17.0...v0.17.1)
- Ensure that generated CDI specs do not contain `enable-cuda-compat` hooks
- Remove nvidia.com/gpu.imex-domain label
- Ignore XID error 109
- Add `ada-lovelace` architecture label for compute capability 8.9
- Ensure FAIL\_ON\_INIT\_ERROR boolean env is quoted
- Honor fail-on-init-error when no resources are found
</details>
---
### Configuration
📅 **Schedule**: (UTC)
- 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.
👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://github.com/renovatebot/renovate/discussions) if that's undesired.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box
---
This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xMy4zIiwidXBkYXRlZEluVmVyIjoiNDQuMTMuMyIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOltdfQ==-->
Reviewed-on: https://forge.superkooka.com/Superkooka/infra-gitops/pulls/131 parent 4c49697 commit d13b252
3 files changed
Lines changed: 3 additions & 3 deletions
File tree
- infrastructure
- cert-manager
- longhorn
- nvidia
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
8 | 8 | | |
9 | 9 | | |
10 | 10 | | |
11 | | - | |
| 11 | + | |
12 | 12 | | |
13 | 13 | | |
14 | 14 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
13 | 13 | | |
14 | 14 | | |
15 | 15 | | |
16 | | - | |
| 16 | + | |
17 | 17 | | |
18 | 18 | | |
19 | 19 | | |
| |||
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
8 | 8 | | |
9 | 9 | | |
10 | 10 | | |
11 | | - | |
| 11 | + | |
12 | 12 | | |
13 | 13 | | |
14 | 14 | | |
| |||
0 commit comments