You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Migrate to internal node implementation of fetch #2306
It relies on the "undici" module instead of using node-provided undici as features like interceptors, middleware, and stream are not yet available in the node native version. https://undici.nodejs.org/#/?id=undici-module
I tested locally regenerating the client. As expected, most of the types in Config that rely on https/node-fetch are subtly different than the undici interfaces and will require updates.
I havent tested the mocking yet. As previously discussed, nock will no longer work for our tests with undici.
Reacted by Max Strübing, Saullo Bretas Silva and 0x5457
Activity
cjihrig commentedon Mar 27, 2025
I think this might also resolve #2127 since native fetch has a
keepaliveoption, which node-fetch does not.EDIT: This is probably wrong. The
keepalivein thefetchspec is something different.begin migration to native fetch()
k8s-triage-robot commentedon Jul 1, 2025
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedlifecycle/rottenwas applied, the issue is closedYou can:
/remove-lifecycle stale/closePlease send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
mstruebing commentedon Jul 1, 2025
/remove-lifecycle stale
k8s-triage-robot commentedon Sep 29, 2025
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedlifecycle/rottenwas applied, the issue is closedYou can:
/remove-lifecycle stale/closePlease send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
mstruebing commentedon Sep 30, 2025
/remove-lifecycle stale
davidgamero commentedon Dec 3, 2025
Upstream PR on the generator has merged to use undici.
OpenAPITools/openapi-generator#22408
It relies on the "undici" module instead of using node-provided undici as features like interceptors, middleware, and stream are not yet available in the node native version.
https://undici.nodejs.org/#/?id=undici-module
I tested locally regenerating the client. As expected, most of the types in Config that rely on https/node-fetch are subtly different than the undici interfaces and will require updates.
I havent tested the mocking yet. As previously discussed, nock will no longer work for our tests with undici.
k8s-triage-robot commentedon Mar 3, 2026
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedlifecycle/rottenwas applied, the issue is closedYou can:
/remove-lifecycle stale/closePlease send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
grahamkrubin commentedon Mar 4, 2026
/remove-lifecycle stale
davidgamero commentedon Apr 17, 2026
linking some PRs here to keep things organized
first regeneration with native undici fetch from upstream #2770
phase 2 with full removal of node-fetch and nock packages #2813
davidgamero commentedon Jul 8, 2026
pre-release 2.0.0-rc.1 with native fetch is live
https://www.npmjs.com/package/@kubernetes/client-node/v/2.0.0-rc.1
feedback from early adopters would very appreciated if you give it a try