Skip to content
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

Update client to kubernetes 1.8 #84

Merged
merged 3 commits into from
Oct 3, 2017

Conversation

mbohlool
Copy link
Contributor

Add update client script and update client to kubernetes 1.8.

Copy link
Contributor

@lwander lwander left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like some resources changed in name, most importantly V1Pod is now CoreV1Pod (breaks the util package). Is this client still backwards-compatible with prior cluster versions?

@lwander
Copy link
Contributor

lwander commented Sep 30, 2017

Looks like the URL path stays the same for CoreV1Pods. When a resource is promoted from a beta track to v1, does the API spec keep the beta resource around?

@mbohlool
Copy link
Contributor Author

I will look into this. Probably I need to change the pre-processing script to keep the names backward compatible. That would benefit all clients. Will update this PR and ping you when it is ready. Thanks.

@mbohlool
Copy link
Contributor Author

mbohlool commented Oct 3, 2017

@lwander I fixed the client generator in kubernetes-client/gen#24 and updated the client here using the new code to see if it fixed the problem. Please take another look.

@lwander
Copy link
Contributor

lwander commented Oct 3, 2017

Looks good - shame the extra parameters are required for all API calls

@lwander
Copy link
Contributor

lwander commented Oct 3, 2017

I'm ready to merge when you are

@mbohlool
Copy link
Contributor Author

mbohlool commented Oct 3, 2017

The other PR is merged. Please merge this one. Thanks.

@lwander lwander merged commit 2c3457d into kubernetes-client:master Oct 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants