Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Interested in adding registry support? #24

Open
akshaya-a opened this issue Mar 23, 2024 · 0 comments
Open

Interested in adding registry support? #24

akshaya-a opened this issue Mar 23, 2024 · 0 comments

Comments

@akshaya-a
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant