Delete Namespace response json deserialization exception about dotnet-kube-client HOT 11 CLOSED

See 9d11ac1 for details of what was fixed. I'll push out a new version shortly.

from dotnet-kube-client.

Just for completeness :)

$ kubectl version

Client Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.3", GitCommit:"2bba0127d85d5a46ab4b778548be28623b32d0b0", GitTreeState:"clean", BuildDate:"2018-05-21T09:17:39Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"windows/amd64"}

Server Version: version.Info{Major:"1", Minor:"11", GitVersion:"v1.11.5", GitCommit:"753b2dbc622f5cc417845f0ff8a77f539a4213ea", GitTreeState:"clean", BuildDate:"2018-11-26T14:31:35Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}

And thanks for the new version.

from dotnet-kube-client.

Thanks!

from dotnet-kube-client.

Hi - thanks for reporting this, I’m going to take a quick look at the OpenAPI document and see what it says we should expect there. What version of K8s are you using?

from dotnet-kube-client.

Ok, this is a little odd - according to the K8s docs, StatusV1.Status is always supposed to be a string (Success or Failure):

https://kubernetes.io/docs/reference/federation/v1/definitions/#_v1_status

Let me play around with an actual instance of the K8s API and see what I get...

from dotnet-kube-client.

Oh, right, never mind - I just realised (need my morning coffee!), this relates to #55.

from dotnet-kube-client.

I will check on the version.

from dotnet-kube-client.

No worries - I'm about to add a fix for this (we recently updated the other resource clients to handle this, but I must have somehow missed the v1/Namespace client).

The problem was that some successful delete operations can return either a StatusV1 or a model representing the resource state before it was deleted (in this case a NamespaceV1, which has the correct properties for deserialisation). Only way to tell is to check the kind and apiVersion in the response body. Which we do now, for certain operations.

from dotnet-kube-client.

You're welcome :)

I have published v2.2.4 (but it may take a while for NuGet to index the packages).

from dotnet-kube-client.

(if you need packages sooner that NuGet can index them, they are also published to this MyGet feed: https://www.myget.org/F/dotnet-kube-client/api/v3/index.json)

from dotnet-kube-client.

Tested and confirmed to be working fine.

from dotnet-kube-client.