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
When performing a watch on a list if the server returns ERROR (kind: status) there is a deserialization error because the status object differs from the Watch.Response. This is particularly prevalent using custom resources. The Watch response handler blindly uses watchType when deserializing which causes the json deserializer to throw an exception when the response object does not match the watch type.
The text was updated successfully, but these errors were encountered:
However, io.kubernetes.client.util.Watch.Response.next() simply deserializes using the target type rather than checking the kind of object and supporting a potential status.
When performing a watch on a list if the server returns ERROR (kind: status) there is a deserialization error because the status object differs from the Watch.Response. This is particularly prevalent using custom resources. The Watch response handler blindly uses watchType when deserializing which causes the json deserializer to throw an exception when the response object does not match the watch type.
The text was updated successfully, but these errors were encountered: