You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've searched the issue queue to verify this is not a duplicate bug report.
I've included steps to reproduce the bug.
I've pasted the output of kargo version.
I've pasted logs, if applicable.
Description
We are using kustomize as the main templating language in our repositories. Sometimes we combine this with helmCharts.
When I want to render such a kustomization template to plain files I receive an error if the kustomization uses helmCharts and specifies a oci:// repository.
Steps to Reproduce
Create a kustomization.yaml which uses a helmChart in your repository inside a kargo directory e.g.
Error: error pre-rendering manifests: error generating manifests using Argo CD repo server: `kustomize build /tmp/3315312386/repo/kargo --enable-helm --load-restrictor LoadRestrictionsRootOnly` failed exit status 1: Error: Error: looks like "oci://ghcr.io/akuity/kargo-charts/kargo" is not a valid chart repository or cannot be reached: object required
: unable to run: 'helm pull --untar --untardir /tmp/3315312386/repo/kargo/charts --repo oci://ghcr.io/akuity/kargo-charts/kargo kargo --version 0.2.0' with env=[HELM_CONFIG_HOME=/tmp/kustomize-helm-4020257331/helm HELM_CACHE_HOME=/tmp/kustomize-helm-4020257331/helm/.cache HELM_DATA_HOME=/tmp/kustomize-helm-4020257331/helm/.data] (is 'helm' installed?): exit status 1
Screenshots
Also tested with kargo v0.2.0 results in the same error as local
Version
Tested with ghcr.io/akuity/kargo-render:v0.1.0-rc.33.
I wanted to test with the version from the docs (ghcr.io/akuity/kargo-render:v0.1.0-rc.25) but this seems no longer available. It results just in
Unable to find image 'ghcr.io/akuity/kargo-render:v0.1.0-rc.25' locally
docker: Error response from daemon: manifest unknown.
See 'docker run --help'.
Additional Notes
I think this is related to this issue which got fixed in kustomize with this PR
ArgoCD also bumped the kustomize version to 5.2.1 with the 2.9.0 Release.
I checked the go.mod file and saw tha kargo-render still uses ArgoCD in version 2.8.4 - if this is already the issue then the open PR would fix my issue already :-)
Greetings,
Jan.
The text was updated successfully, but these errors were encountered:
I checked the go.mod file and saw tha kargo-render still uses ArgoCD in version 2.8.4 - if this is already the issue then the #221 would fix my issue already :-)
I love it when it's that simple!
I will forewarn you, however, that main has significant breaking changes to the schema for the kargo-render.yaml file, so while an upcoming rc.34 may fix your issue, you will also have to update your config.
We will, of course, document those changes. Just didn't want you caught by surprise if you happened to build from source.
Checklist
kargo version
.Description
We are using kustomize as the main templating language in our repositories. Sometimes we combine this with
helmCharts
.When I want to render such a kustomization template to plain files I receive an error if the kustomization uses
helmCharts
and specifies aoci://
repository.Steps to Reproduce
Create a kustomization.yaml which uses a
helmChart
in your repository inside akargo
directory e.g.Add a kargo-render.yaml
Run local docker
Receive error
Screenshots
Also tested with kargo v0.2.0 results in the same error as local
Version
Tested with
ghcr.io/akuity/kargo-render:v0.1.0-rc.33
.I wanted to test with the version from the docs (
ghcr.io/akuity/kargo-render:v0.1.0-rc.25
) but this seems no longer available. It results just inAdditional Notes
I think this is related to this issue which got fixed in kustomize with this PR
ArgoCD also bumped the kustomize version to 5.2.1 with the 2.9.0 Release.
I checked the go.mod file and saw tha kargo-render still uses ArgoCD in version 2.8.4 - if this is already the issue then the open PR would fix my issue already :-)
Greetings,
Jan.
The text was updated successfully, but these errors were encountered: