Interested in adding registry support?

[akshaya-a]

Maybe I'm using this wrong but I feel like a common CI case would be to

docker build
docker push <>
k3d/s deploy app based on docker image

For this scenario, I'm using a k3d managed local registry, which is difficult (maybe) to use with the current action here.

I think the action should take a new create_registry and port args (both optional) and if set
create the registry, then
create cluster referencing it
(makes it easier to deterministically set port for downstream docker push vs uber command that creates cluster + registry on random port)

or are people doing something else?

[nolar]

One way that I used on my dev machine was importing the locally built image directly into the k3d/k3s cluster with k3d image import img:tag and then using it for containers — the same can work in GHA with this action (k3d is installed). So, the image becomes available under its name — as published (or as built at least), without tweaking the registry prefixes, which are a part of the name.

But the registry approach can be interesting, though adds complexity. I will think on this.