k3d-io
Registry not prefixed with `k3d`
When creating a new registry, it sometimes gets prefixed with k3d (i.e. DefaultObjectNamePrefix) and sometimes not. This inconsistency should be fixed for a better user experience.
Running the following creates a registry called k3d-foo:
k3d registry create foo --port 127.0.0.1:1234
Running the following creates a registry called foo:
k3d cluster create --registry-create foo:127.0.0.1:1234
The comment here says that "DefaultObjectNamePrefix defines the name prefix for every object created by k3d", which is clearly not true.
Clearly, the registry is created without the prefix when using k3d cluster create --registry-create:
https://github.com/k3d-io/k3d/blob/72726ef6082b20a027fef3c64220f3d7daf6ce14/cmd/cluster/clusterCreate.go#L578
Best would be if we could make DefaultObjectNamePrefix optional, because it can sometimes be nice to be able to override it (e.g. to create a local registry with the exact same name that a remote registry have).
Encountering this now. Is there a way to avoid the prefix?
I think that when i used this https://github.com/oshoval/k3d_kubevirt/blob/main/cluster-up/cluster/k3d/common.sh#L131 https://github.com/oshoval/k3d_kubevirt/blob/main/cluster-up/cluster/k3d/common.sh#L135 it was stable ah maybe because of the rename that i did (L132) which does assume there is k3d (but for me it was stable) you can maybe detect, and rename to something fix, covering both cases as WA
