tilt-dev/k3d-local-registry

Compatible with K3d 1.x only

DblK opened this issue · 6 comments

DblK commented

Since I am a mac user, when I update homebrew it installed k3d v3.
They did not left the k3d 1.7 binary.

So just for information, waiting for k3d 3.0 compatible script, I have created a tap to install it.

nicks commented

thanks for the report!

ya, I think k3d had some issues with this release and they cut the registry stuff to get the release out
https://github.com/rancher/k3d/releases/tag/v3.0.0

there's an effort underway to use a registry discovery protocol in k3d v3.1.0 so that this script becomes unnecessary, see:
k3d-io/k3d#234

Tchoupinax commented

Hello,

I relaunch this issue with the release yesterday of the version 4 of k3d.

The interesting feature is the registry support :

image

I think we could rewrite this script with the new release of k3d now it has the registry support. I'm very interested by this update because I use this script to launch all my cluster.

What is the roadmap about this subject ? Maybe I could work on it and offer you a pull request with the new version, but I want to know before if you thought about another direction (like the registry discovery protocol like you mentionned in your previous post).

Keep me informed.
Thank a lot for your work ! <3

nicks commented

Hi @Tchoupinax !

We've been working with the k3d team on this! In theory, the new k3d flags should make this script entirely obsolete, since now k3d handles internally everything that this script handles.

I've been testing it out and filing bugs. Plan is to deprecate this repo and point to the k3d instructions once we've verified it. Have you had a chance to try it?

  • 👍1
  • ❤️1
Tchoupinax commented

Hello @nicks !

Great new !
However, I do not have time yet to explore the new version and to migrate with the new intructions. I saw that the new version provides a "proxy" to free the port 6443 (and maybe have several cluster at the same time I think ? Yeahhh!!).

Yeah, we could deprecate this repo, I only think that if instructions are not clear with k3d docs, It would be very nice to archive this repo and add a section on the readme "Migrate to v4.x" with the equivalent instructions (for current and future users). :)

nicks commented

I updated the README with a link to K3d v4.0's instructions!

Tchoupinax commented

Thanks !