Tomasz Prus

Sure, conflicts resolved.

Is it self-hosted cluster or provided by Google/AWS/Azure? Could you check if `kubectl` works longer without the issue?

There is a flag `--watch` to watch for changes, for example: `kubectl get pods --watch`

How long is it working without raising the exception? I'm also not sure what to do... we can treat it as "timeout" and silently reconnect but on the other hand...

Yes, it's on my TODO list.

As you checked, patching custom objects supports `application/merge-patch+json` only so I guess API Server (or CRD) rejects a request with different type of merge, doesn't it?

Fixed in the latest release - v10.0.0

Thanks, definitely it needs to be fixed.

Could you tell more about your use case? Do you try to use different merge strategy?

Thanks. As a workaround you can try to send list with [JSON Patch](http://jsonpatch.com/) instructions to modify your CRD. This nice library https://github.com/stefankoegl/python-json-patch creates such patches from differences between dicts.