-
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
Failed to create namespaced custom object with new Kubenertes Client 11.0.0 #1112
Comments
/assign |
@roycaihw Any plan to fix this? Thanks. |
@jinchihe I got the same problem, did you solved it? |
Thanks, it works for me |
Add this to the api_client line ~215, solved the issue for now. |
hello @roycaihw and all, I found the problem still exists in 12.0.0, any plan to fix the problem? this is a block issue. Thanks. |
Seems that's cuased by kubernetes client use openapi_types instead of swagger_types from 11.1? |
Need to update the generate openapi_types for the crd before calling k8s client. |
Sorry for the late response. Yes we've switch the code generator from swagger codegen to openapi generator, and the attribute was renamed from swagger_types to openapi_types. If you generated models for your custom resources, you need to regenerate them using openapi-generator. You could also use the dynamic client to access custom resources, which do not have this issue. |
Yeah, I already did that. Thanks. |
@roycaihw
method and this method also has this issue in version 11.0.0 and 12.0.0. Note that these are not custom resources. |
@jinchihe Thanks |
What happened (please include outputs or screenshots):
Failed to create namespaced custom object with new Kubenertes Client 11.0.0
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
kubectl version
): 11.0.0python --version
)pip list | grep kubernetes
)The text was updated successfully, but these errors were encountered: