Errors from @kubernetes/client-node returned as "{}"
See original GitHub issueWhat is wrong: Errors from @kubernetes/client-node returned as “{}”
Why: Properties of the Error object are not enumerable.
From the documentation of JSON.stringify(),
For all the other Object instances (including Map, Set, WeakMap and WeakSet), only their enumerable properties will be serialized.
Possible solutions: https://stackoverflow.com/questions/18391212/is-it-not-possible-to-stringify-an-error-using-json-stringify
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
node.js - Running NodeJs kubernetes client example error
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not...
Read more >TypeScript - watch-example - not working · Issue #401 - GitHub
I copy-pasted the example, and exported a module, here goes: const k8s = require('@kubernetes/client-node'); const kc = new k8s.
Read more >Troubleshooting kubeadm | Kubernetes
In some situations kubectl logs and kubectl run commands may return with the following errors in an otherwise functional cluster:.
Read more >Invoking the Kubernetes API in Node.js - DEV Community
kubernetes -client outputs a HTTP error when a request fails. The following example emulates kubectl apply , by handling a 409 Conflict error...
Read more >Top 5 @kubernetes/client-node Code Examples - Snyk
key !== singleOperatorName) { console.log(`\n\nOPERATOR ${operatorDefinition.key}\n - skipping`); return ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@dot-i Thanks Nico for a quick fix. Your library is very helpful and I appreciate the work you’ve done!
Should be fixed in
1.0.16
now 🤞