Skip to content

Issues: kubernetes-client/javascript

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

30 Open 607 Closed
30 Open 607 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

updating package version results in ES Module errors when using NestJs
#2219 opened Feb 10, 2025 by dbrcplex
8
body/class definitions missing
#2218 opened Feb 10, 2025 by mStirner
4
"server" must be an instance of URL
#2202 opened Feb 4, 2025 by BenSaxon
2
Publish docs
#2190 opened Jan 31, 2025 by cjihrig
4
Type Error. ObjectSerializer expects a date but I want to pass it a string
#2189 opened Jan 31, 2025 by BenSaxon
1
Switch to version 1.0.0 : node-fetch behind proxy
#2161 opened Jan 14, 2025 by Leer0r
2
Patch fails with error decoding patch: json: cannot unmarshal object into Go value of type []handlers.jsonPatchOp
#2160 opened Jan 14, 2025 by yubinnng
10
403 Forbidden with system:anonymous using Kind cluster and @kubernetes/client-node 1.0 with Bun 1.1.29
#2157 opened Jan 9, 2025 by jbiskur
8
Callback not getting invoked for exec call
#2133 opened Dec 30, 2024 by quoctruong
3
Watch keepalive not working anymore with 1.0.0
#2127 opened Dec 27, 2024 by Alabate
1
4
1.0.0 released - where are the migration docs?
#2117 opened Dec 19, 2024 by klippx
10
Test and Replace patch fails but works with kubectl
#2095 opened Dec 7, 2024 by TNonet
4
Inconsistent deserialization behaviour when using KubernetesObjectApi.list vs KubernetesObjectApi.get
#2018 opened Nov 8, 2024 by LFrobeen
2
Upgrade to 0.22.2 fails due to use of new major version of client-node.
#2014 opened Nov 4, 2024 by TonyJDavies
17
informer's cache is empty after await informer.start() lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
#1952 opened Oct 18, 2024 by atamon
7
Using middleware with 1.x clients lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
#1925 opened Oct 11, 2024 by memoselyk
3
CustomObjectsApi.deleteCollectionNamespacedCustomObject does not support several OpenAPI query parameters good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
#1778 opened Jul 9, 2024 by rotty3000
@ArpanSolanki29
7
not possible to set a client timeout good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines. javascript Pull requests that update Javascript code
#1613 opened Mar 12, 2024 by cdbkr
8
1.0.0-rc4 Example for overriding the content-type header of patching operations do not work lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#1499 opened Jan 4, 2024 by tugtugtug
11
Generated API hides kubernetes REST API response result lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
#1498 opened Jan 4, 2024 by jimjaeger
10
ECONNRESET error from kubernetes watch after some minutes.
#1496 opened Jan 2, 2024 by jimjaeger
10
Misleading watch example uses watchObj.metadata.resourceVersion lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
#1493 opened Jan 1, 2024 by jimjaeger
8
cpFromPod / cpToPod is missing --retries flag good first issue Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
#1407 opened Nov 9, 2023 by PeterEinberger
2
LimitRange default field missing lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#855 opened Aug 11, 2022 by zabealbe
4
Timestamps have wrong type lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#487 opened Aug 17, 2020 by simhnna
25
ProTip! no:milestone will show everything without a milestone.