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

Check what needs to be upgraded for client-go v6 #171

Closed
asymmetric opened this issue Jan 30, 2018 · 5 comments
Closed

Check what needs to be upgraded for client-go v6 #171

asymmetric opened this issue Jan 30, 2018 · 5 comments

Comments

@asymmetric
Copy link
Contributor

asymmetric commented Jan 30, 2018

There are some changes to be made. Off the top of my head:

@lilic
Copy link
Contributor

lilic commented Jan 30, 2018

I do not understand this issue, we are already at client-go v6.0.0?

@asymmetric
Copy link
Contributor Author

Yes, but we haven't performed the changes in our codebase that can/should go along with it.

@lilic
Copy link
Contributor

lilic commented Jan 30, 2018

Yes, those are nice to have, but not necessary to have things working. As deployments is supported for at least 1.9.x, maybe even more. This way we do not break compatibility with older k8s versions.

getting rid of newListWatchFromClientWithLabels

Why is this needed?

@asymmetric
Copy link
Contributor Author

That's a good point about compatibility. But at some point we have to update (v1beta1.Deployment will be deprecated and then removed at some point, I presume), and this issue can be useful to list what we need to do.

I edited my post above to answer your second point.

@lilic
Copy link
Contributor

lilic commented Jan 30, 2018

(v1beta1.Deployment will be deprecated and then removed at some point, I presume)

There is ongoing discussion upstream to not deprecate versions as fast as it is currently, we will see what comes out of that.

This was referenced Apr 24, 2018
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

No branches or pull requests

2 participants