-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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-go to v12.0.0 #732
Comments
Relatedly please know that the library form is significantly less stable, @munnerz and I have been working on a plan to clear that up, expect future versions of the library to change quite a bit. We export much more than we should. |
Thanks for the heads up @BenTheElder, currently I only have a lightweight integration. I will be cautious about going deeper with that integration. 👍 |
We're still working on the library interface but it's actively coming along 😅 I beleive #744 removed client-go from being tracked here. |
When trying current master it seems that #744 didn't stop client-go from getting pulled in at In case others run into this I've just been using a simple workaround in my
|
thanks! I admit i've not imported a recent version of kind into another project yet, I'm currently working on refining the library surface and usability more. I think the replace is probably the right solution long term, it looks like we'll want to actually start using client go for #850 in the future possibly... |
What should be cleaned up or changed:
Currently if you want to include
kind
as a library in another tool it will hold yourclient-go
version atv11.0.0
by default. The latest release forclient-go
is now v12.0.0 and it would be helpful to update kind to this version.Why is this needed:
This makes it a bit easier to integrate with
kind
as a library.The text was updated successfully, but these errors were encountered: