V4: Private registry and k3d managed registries

[andrejpetras]

Hi,

I do have a private registry which I would like to use in the local k3d cluster but also I would like to use the local registry managed by the k3d.
Would it be possible to use --registry-create or --registry-user in version 4 together with custom registries.yaml?

I try the combination, but it does not work for me. Looks like the --registry-create or --registry-use always generated new registries.yaml file. Would it be possible to do merge instead?

BR,
Andrej

[iwilltry42]

Yay, our first directly opened discussion 🎉

But first: Hi and thanks for testing v4 🙂

That's actually a case I missed to consider while writing this.
I'll put this on the todo for the upcoming GA release. However, I need to do some testing as to when this should happen (i.e. at what time is the mounted file present in the container file system) etc.
I'll do some investigation there 👍

[andrejpetras]

@iwilltry42 thank you for your quick response

Currently, we do have simpleconfig.yaml and registries.yaml, and we need to reference to the registries.yaml file with absolute path.

Could we add private registry to the SimpleConfig or ClusterConfig to have the configuration in one place?
We do not need to merge registries.yaml files but only generate one registries.yaml base on the configuration.

Please let me know if I can help you any further

[iwilltry42]

This will be tackled in this feature request: #451
Thanks for your input :)