-
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
get_api_group() raises ValueError: Invalid value for server_address_by_client_cid_rs
, must not be None
#394
Comments
I'm still confused. When I look at the documentation for get_api_group() at https://github.com/kubernetes-incubator/client-python/blob/master/kubernetes/docs/ApiextensionsApi.md#get_api_group ,
It shows get_api_group() being called with no arguments, exactly like I called it. Where are these fields supposed to be set? Is the documentation wrong, or something else going on? The way configurations are done in the documentation is now different from the way it's done in the examples under the main tree. Documentation:
Examples:
I haven't changed any of my configuration code, it uses the method given in the examples, which is the same as for 3.0. Does this no longer work? |
After taking a look at this in the debugger, this is either a bug or a configuration problem on the Kubernetes side. In the other issue that @tomplus mentioned, they're constructing a pod by instantiating the model classes directly. I'm not hand-creating V1APIGroup at all, I'm making a call against get_api_group(). The client receives the HTTP response and decodes it into a Python dict using the json module inside deserialize():
Here, response_data is:
json.loads turns this into:
It sets Are all Kubernetes clusters required to have serverAddressByClientCIDRs set to a non-null value? This cluster is freshly installed with 1.8 using Kubespray. I can't reopen this issue, could you please reopen it? |
The question is why Kubernetes returns None, this field is mandatory. There is a notice that "The server returns only those CIDRs that it thinks that the client can match." (https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.9/#apigroup-v1-meta). Maybe it works only from the cluster (when an application is deployed to cluster)... |
server_address_by_client_cid_rs
, must not be None
server_address_by_client_cid_rs
, must not be None
I think this may be an issue of the translation to python by swagger. It's possible that the field is required, and that I'm not sure if other languages will see the same issue, but it may be a limitation of the spec, and we may need to figure out a better way to handle it. I think we need to be able to differentiate between the case that it is |
Umbrella issue: kubernetes-client/gen#52 |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
When I call get_api_group() with the 4.0 beta client against Kubernetes 1.7 or 1.8, I get an error:
Not sure if this is a misconfiguration issue or something deeper.
The text was updated successfully, but these errors were encountered: