-
Notifications
You must be signed in to change notification settings - Fork 16
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
release kargo-render binary #284
Comments
Kargo proper just did something about this a few days ago: akuity/kargo#1977 I had been imagining that we'd soon create a native way for chart repo creds to be passed directly to Kargo Render as well, but hadn't yet put much thought into how. On some level, I'd prefer solving that over simply publishing the binary, since there is a reason that we don't. (Packaging it in an image with git, helm, and kustomize binaries is the easiest way to guarantee Kargo Render has compatible versions of those binaries available to it.) I'll start thinking about a clean way of passing the creds through. |
Fair points. |
You can also copy it out of a container as long as you're looking for linux/amd64 (or linux/arm64). Presumably in an Action, linux/amd64 would be exactly what you need. |
To put some closure on this, solving for #226 will obviate the need for this. |
Currently, only the Docker image is published. It would be great to also provide a binary release. Currently, it's challenging to pass through Helm credentials in a GitHub Action because it's within a container with its own Helm installation.
Having a binary release would allow the
kargo-render
binary to be used within the workflow authentication context.The text was updated successfully, but these errors were encountered: