-
Notifications
You must be signed in to change notification settings - Fork 38.7k
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
Improve the output of the swagger API for watch events #6232
Improve the output of the swagger API for watch events #6232
Conversation
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project, in which case you'll need to sign a Contributor License Agreement (CLA) at https://cla.developers.google.com/. If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check the information on your CLA or see this help article on setting the email on your git commits. Once you've done that, please reply here to let us know. If you signed the CLA as a corporation, please let us know the company's name. |
LGTM. Thanks. @thockin can rebase on top of this and regenerate the swagger. |
Tests are failing:
|
Merged multi-port services. Please run hack/update-swagger-spec.sh. |
9bc21fe
to
b672965
Compare
18726d9
to
54162c5
Compare
Rebased, test fixed, and docs updated. ----- Original Message -----
|
"v1beta3.ServiceSpec": { | ||
"id": "v1beta3.ServiceSpec", | ||
"required": [ | ||
"ports", | ||
"port", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Something's not right here. This is reverting multi-port services, among other things.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bad merge, let me delete and regen.
----- Original Message -----
"v1beta3.ServiceSpec": { "id": "v1beta3.ServiceSpec", "required": [
"ports",
"port",
Something's not right here. This is reverting multi-port services, among
other things.
Reply to this email directly or view it on GitHub:
https://github.com/GoogleCloudPlatform/kubernetes/pull/6232/files#r27528460
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed, sorry.
----- Original Message -----
Bad merge, let me delete and regen.
----- Original Message -----
"v1beta3.ServiceSpec": { "id": "v1beta3.ServiceSpec", "required": [
"ports",
"port",
Something's not right here. This is reverting multi-port services, among
other things.
Reply to this email directly or view it on GitHub:
https://github.com/GoogleCloudPlatform/kubernetes/pull/6232/files#r27528460
54162c5
to
6de6a8d
Compare
Weird. I'm not seeing the comments I received via email, nor the latest push. |
@smarterclayton Maybe try to make clean, rebuild, and regenerate the swagger? @nikhiljindal Any guess about what's going on with the swagger generation? A stale go-restful dependency? |
@smarterclayton : Did you rebuild the binary before running update-swagger-spec? |
@nikhiljindal He picked up some recent API changes, so I'd guess he did build it. |
Ok, sorry. Swagger has been updated from earlier changes. Please rebase and re-update swagger again. Feel free to self-merge. |
6de6a8d
to
00c32cf
Compare
@smarterclayton Could we try to get this in before something breaks it again? :-) It might be easier if you didn't update the swagger in this PR. |
Stopgap to improve this prior to converting watch resources to versioned objects.
00c32cf
to
66ec02f
Compare
Rebased, split swagger out. |
LGTM. Thanks. When looking at this I noticed that the /log content types are wrong. The shippable failure is a known kubelet test problem. |
…gger Improve the output of the swagger API for watch events
Stopgap to improve this prior to converting watch resources to
versioned objects.
Spawned from #6182