cluster: create k3d from a config file.

[nicks]

fixes #224

Signed-off-by: Nick Santos nick.santos@docker.com

[nicks]

ack, most of this is just wrangling the api infra. i was working on better configs for lightweight clusters and it got out of control 🥵

[almereyda]

Many thanks for this. Indeed the types went out and about.

If I may ask, is there any way to support --default-network with created registries, in so that the custom-network is used in their instantiation? I couldn't find any struct property to carry this data. It would also be some kind of hack, since this property is not present in the registries.yaml specification and K3d does not directly offer to create registries from a YAML manifest (without involving a cluster). --default-network remains available only as a CLI argument. Eventually ctlptl would want to wrap that?

This is generally useful for getting K3d to work on top of Podman, because it does not have a default bridge to which the registry could be connected. That assumes the network, to which registry and cluster will be connected, is created in advance.

[krancour]

The new k3d config support works great! I just wanted to say thank you!