[QUESTION/HELP] With a k3d created registry can I specify the port that it maps onto?

[Data-drone]

With a k3d created registry can I specify specific port that the registry binds to?

How can I configure this in a cluster definition yaml?

[iwilltry42]

Hi @Data-drone , thanks for asking!
Currently (v4.4.8), the --registry-create flag is a simple boolean that takes some defaults and assigns a random port. More specific configuration can be done using the separate argument k3d registry create which offers more configuration options.
Additionally, the soon-to-come k3d v5.0.0 release enables a string parameter on --registry-create to allow more configuration from there (and also in the config file).

You can already give it a try:

• Pre-Release: https://github.com/rancher/k3d/releases/tag/v5.0.0-rc.1
• Docs: https://k3d.io/v5.0.0-rc.1/usage/registries/#using-k3d-managed-registries
• PR: [Enhancement] More powerful registry-create opt #727
• Command help:

    --registry-create NAME[:HOST][:HOSTPORT]                         Create a k3d-managed registry and connect it to the cluster (Format: NAME[:HOST][:HOSTPORT]
                                                                       - Example: `k3d cluster create --registry-create mycluster-registry:0.0.0.0:5432`
  

[Data-drone]

How long does it typically take to go from rc to release?

[iwilltry42]

As long as it takes me to iron out the last bugs 😬
Right now I only need to fix an issue with the DNS workaround on Mac, which is a bit tricky for me since I don't have a Mac and now first need to setup a VM with nested virtualization, etc. to test my changes 🙄
I hope to release tomorrow 👍