-
Notifications
You must be signed in to change notification settings - Fork 297
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
V1Status not deserialized on DeleteNamespaceAsync #1154
Comments
10.0 is based on 1.26 see #824 |
Hi, Before posting the issue I'd visited the #824, the reported issue is on deletion of a service, mine is deleting the namespace. I've downgraded the client to v9.1.3 and observed the same behavior. Do you think I should downgrade the client to a previous version? I'll also ask to upgrade the cluster version to v1.26.x |
could you please give 7.2 a shot? |
I've evaluate a downgrade to 7.x but it will break the code, it was easier to upgrade the cluster to v1.25.4, so I give a try with client 9.1.3, the V1Status did not deserialized, only the property HasObject is set to true, no exception was raised; unfortunately I can't request a cluster upgrade to v1.26.x to try with client 10.x. |
Describe the bug
Just call the method on an existing namespace
Kubernetes C# SDK Client Version
10.0.1
Server Kubernetes Version
1.23.5
Dotnet Runtime Version
net7
To Reproduce
Call the DeleteNamespaceAsync with arguments:
ns: "existing namespace"
pretty: true
propagationPolicy: Foreground
Expected behavior
V1Status return object with most property values different of null
Where do you run your app with Kubernetes SDK (please complete the following information):
The text was updated successfully, but these errors were encountered: