Workaround deserialization errors in Node API

[olix0r]

We recently noticed some unexpected deserialization errors when reading core::v1::Node values. It turns out that there's a serialization bug in Kubernetes that can cause the names field to be encoded as null when it should be encoded as [].

I've created a branch with a small workaround and it looks like they intend to implement a similar workaround in the Python client.

Is there any interest in picking up a workaround in this repo? If so, do you have any pointers about how best to go about this in a way that will be maintainable until a Kubernetes fix is broadly available? Until such time, it's virtually impossible to use the Node API reliably with this library.

[Arnavion]

Duplicate of #93

[olix0r]

@Arnavion sorry for the noise! thanks for the fix :)