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
Describe the bug
When using k8s.topNodes an exception is thrown:
/home/user/tmp/k8s-client-node/node_modules/@kubernetes/client-node/dist/top.js:61
pod.status.phase === 'Running' || pod.status.phase === api_1.V1PodStatus.PhaseEnum.Running);
^
TypeError: Cannot read properties of undefined (reading 'Running')
at /home/user/tmp/k8s-client-node/node_modules/@kubernetes/client-node/dist/top.js:61:92
at Array.filter (<anonymous>)
at Object.topNodes (/home/user/tmp/k8s-client-node/node_modules/@kubernetes/client-node/dist/top.js:59:21)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async main (/home/user/tmp/k8s-client-node/main.js:9:21)
** Client Version **
e.g. 0.20.0
** Server Version **
e.g. v1.24.9 (also tested in 1.26)
Describe the bug
When using
k8s.topNodes
an exception is thrown:** Client Version **
e.g.
0.20.0
** Server Version **
e.g.
v1.24.9
(also tested in 1.26)To Reproduce
Expected behavior
the
topNodes
promise should resovle and return a list of resourcesEnvironment (please complete the following information):
Additional context
The issue was introduced after 0.18.1
The text was updated successfully, but these errors were encountered: