-
Notifications
You must be signed in to change notification settings - Fork 494
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
Updating to version 0.11.0 broke working functionality when using 0.10.2 #370
Comments
It's definitely possible. Is there any chance you can capture the body in both cases and see what/if the difference is? My guess is that the default patch content-type changed between versions. |
Any recommendation on how to capture the body ? I definitely can try but I just have seen the response being captured, not the body. Also, in case it helps, my code is listed below, notice how I needed to add the content-type header explicitly.
|
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. |
/lifecycle frozen |
Hi, coming from #444 and #413, which both seems that @brendanburns I think I have some bandwidths to dig into this and possibly create a PR, but can you provide a bit more info? For example, how swag spec is affecting the typings for Typescript, etc? Thanks. |
Any update on this? I would like to define a new V1Service object and the targetPort is an |
Hi, we have a very basic app that executes a kubectl patch command to add an annotation on a deployment, when using v0.10.2 works fine, but when using v0.11.0 it doesn't throw any errors but the patching action to add the annotation is not performed. Looking at changes introduced on v0.10.3 an v0.11.0 noticed that K8s openAPI spec was upgraded from v1.13.10 to v1.15.5.
Our clusters are currently in k8s v1.13.9, would the openAPI update explain why our app stopped working when using 0.11.0 ?
thanks for any clarification that can be provided
The text was updated successfully, but these errors were encountered: