-
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
v1beta1/create_namespaced_deployment_rollback #491
Comments
Hi @tomplus, in this case we have |
Sorry, you are right. I've deleted my previous comment to remove the link from the attached issue. It looks like bug in official API specification. Take a look - https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.9/#rollback IMO you can create an issue here: https://github.com/kubernetes/kubernetes/ |
Hi, thank you for that great pointer I didn't noticed before ! Thank you, regards ! |
k8s PR tracked here: kubernetes/kubernetes#56591. Closing |
The fix does not seem shipped into pip package, I have to use _preload_content=False to prevent client from parsing the response. |
Yeah I'm still running into this as well, thanks for the tip to at least get around it for now @zq-david-wang |
The k8s openapi fix was merged after 1.11 and didn't get cherrypicked. Currently the latest python client (v7) is generated from k8s 1.11, so it still doesn't include the fix. We will release v8 after k8s 1.12 is released, and the client will include the fix. |
Actually I realized that the previous fix was wrong kubernetes/kubernetes#63837 (comment). I had another fix kubernetes/kubernetes#68864 and plan to cherrypick it to 1.12.1 (talked with 1.12 patch release manager-- 1.12.1 release will be roughly two weeks after 1.12.0 being cut). @yliaog I plan to do an alpha release align with 1.12.0 and a beta release align with 1.12.1, assuming that we don't have more API change after beta release. WDYT? |
that sounds good to me. |
Hello, I'm running into this issue as well with: Python kubernetes==9.0.0
Was there a fix for this one? Cheers, |
Oh, that was my bad. I was misusing the API! :( |
Hello, I'm getting some issues trying to rolling back a deployment because api-client response.
If I try to run an the examples' deployment script I'm getting this error during rollback:
Tracing api calls, this is what is posted during rollback:
Response, a positive
201 Created
, is:I don't think this could be related to
rollbackTo
deprecation in v1beta1, cause if I rollback viakubectl rollout undo
as documented here I still get a similar chat (altough norevision
in $.rollbackTo).I think the culprit is on swagger machinery but I don't know if it could be safe to work on this, or what else.
Any ideas ? Thank you, ciao !
The text was updated successfully, but these errors were encountered: