Use 'kind get kubeconfig' instead of deprecated 'kubeconfig-path'

[stv0g]

kind get kubeconfig-path has been removed in kubernetes-sigs/kind@e258374

The PR uses kind get kubeconfig and writes the contents into a local file.

Closes #1650

[manics]

Thanks for this PR, CI tests are still passing with the current version of kind 👍 .

What do you think about moving the duplicated code into a new method e.g. get_kubeconfig() or get_kubeconfig_path()?

[stv0g]

Hi @manics,

I refactored the duplicated code into a new function as you proposed.

[consideRatio]

@stv0g thank you for your contribution and @manics for your review! ❤️

I've felt that the local development experience with this dev script and the way it use kind isn't good enough, and suggest we kill it entirely in favor of k3s (and optionally k3d which wraps k3s in docker containers).

In #1664 I'm removing the dev script and the use of kind. I created the dev script an feel it was a big failure because of how much complexity it added and how fragile it behaved. I hope that by killing it now rather than later I will spare others the time wasted on interacting with it.

With this considered, does it feel okay to close this PR @stv0g?

[stv0g]

@consideRatio I agree.

Are you planning to use the new dev setup also for CI tests?

I was trying to get the CI tests ready for IPv6. Unfortunately, kind's IPv6 support is broken :(

[consideRatio]

@stv0g yepp thats the plan - local dev + CI environment.

I'm not sure about k3s ability to work with ipv6 or not, I'm very inexperienced in general about ipv6 so far.

[consideRatio]

Seems like bleeding edge support in k3s for ipv6 at best: k3s-io/k3s#284

[stv0g]

At least the Rancher UI is not capable of IPv6 :(

[consideRatio]

@stv0g I hope to be able to help you help everyone with the IPv6 support, I'm slowly catching up with a backlog of things to do.

[consideRatio]

We have now replaced kind entirely with k3s in our CI setup, and the local dev setup instructions are updated to use k3s or k3d.