-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Creating a custom resource definition works on 1.7 and fails on 1.8 with 4.0 client #415
Comments
It looks like kubernetes 1.7 made the statement that nulls and empty arrays should be treated the same: https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG-1.7.md#known-issues This also related to this open bug: #376 |
Is there an ETA on getting this fixed? It's still broken in 5.0.0b1 and I would like to be able to upgrade my clusters. |
We'd love to see a fix as well. For now, we've put in the following patch in our code:
|
That is a bit gross but I guess will have to do for now... I did create a pr to fix it so hopefully it gets merged and released sometime soon. |
dup of #376 |
I'm using python-client 4.0.0 and Kubernetes server 1.8.0 on minikube. I'm creating a custom resource definition using the
kubernetes.client.ApiextensionsV1beta1Api.create_custom_resource_definition()
API.This calls the following rest endpoint:
https://192.168.64.34:8443/apis/apiextensions.k8s.io/v1beta1/customresourcedefinitions
with the following body:
With Kubernetes 1.8.0, I get the following response:
which generates the following error in the python client:
Kubernetes 1.7.5 returns the following:
This works just fine. The difference is in the return value of the
conditions
fieldNow, there are a few things going on here:
[]
for 1.7.5 andnull
for 1.8.0.plural
andkind
members of theacceptedNames
dict. This really indicates no value, but the swagger says it's required.This could possibly be split into separate issues. Let me know what's best in this case. Thanks!
The text was updated successfully, but these errors were encountered: