Using oci:// prefix in repository errors with not valid chart error #10823
Comments
jgwest
added
component:core
|
I got the same error: rpc error: code = Unknown desc = I checked the original helm pull command. Gives the same error: After that the same but without the --repo clause and directly with the correct oci url: So the problem is not the oci:// prefix; it is the --repo clause that is not supported. Isn't it ? |
|
I run into the same error, managed to workaround it by splitting & moving the For example using the orignal posted error would look like the following:: Give it a go, that fixed it for me. Update: Was reviewing my config and I'm not using it exactly as described, as I've a private |
|
This is also breaking using Bitnami's helm charts as they migrate to OCI spec. As far as I can find, there isn't a way to use their public oci images through argo at all. Adding the repoargocd repo add registry-1.docker.io/bitnamicharts/keycloak \
--type helm \
--name keycloak \
--enable-ociResultRepository 'registry-1.docker.io/bitnamicharts/keycloak' addedTry to create an appargocd app create keycloak \
--repo registry-1.docker.io/bitnamicharts/keycloak \
--helm-chart keycloak --revision 1 \
--dest-namespace keycloak \
--dest-server https://kubernetes.default.svc \
--sync-policy auto Result
Cannot be created via the UI
Apply via helmhelm install my-release oci://registry-1.docker.io/bitnamicharts/keycloakResult
|
|
@cloudymax, I got it working with the following: # leave off the chart part when creating the repo
argocd repo add registry-1.docker.io \
--type helm \
--name docker \
--enable-oci
# specify the full path to the chart and set the revision to one listed here:
# https://github.com/bitnami/charts/blob/main/bitnami/keycloak/Chart.yaml#L31C10-L31C16
argocd app create keycloak \
--repo registry-1.docker.io \
--helm-chart /bitnamicharts/keycloak --revision 15.1.6 \
--dest-namespace keycloak \
--dest-server https://kubernetes.default.svc \
--sync-policy auto |
|
In case that someone want to use OCI repos and configure it in declarative way via official chart (https://argoproj.github.io/argo-helm) there is an example which works for our installation. values.yaml application.yaml |
in argocd config we have repo created successfully with success connection but if we want reuse helm as dependancy in Chart.yaml (oci:// required here) I receive error in Argocd
|
|
@azhurbilo is this what you are seeing? #14636 |
|
Here is what worked for me Step 1 - Add a repositoryargocd repo add ghcr.io --type helm --name stable --enable-ociStep 2 - Create your Application fileapiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: operator-lifecycle-manager
namespace: argocd
spec:
project: default
source:
chart: cloudtooling/helm-charts/olm
repoURL: ghcr.io
targetRevision: 0.26.0
helm:
releaseName: olm
syncPolicy:
automated:
prune: true
selfHeal: true
destination:
server: 'https://kubernetes.default.svc'
namespace: infra |
|
adding in my set up in case it helps anyone. Here is my oci helm chart only: Here is local values.yaml with remote oci chart This is for a very specific type of resource, but the helm valueFiles with the local repo are the only thing that worked for me |
|
I also like to have oci:// prefix working to make interoperability with fluxcd and other systems. |
this fixed it for me |
|
I looked at the solution provided here, here, and here, and seemingly I'm still struggling. Here's what I've done so far. Step 1: add File: apiVersion: v1
kind: Secret
metadata:
labels:
argocd.argoproj.io/secret-type: repository
name: docker
namespace: argocd
stringData:
url: registry-1.docker.io
name: docker
type: helm
enableOCI: "true"Command to apply: I see the Step 2:
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: mariadb
namespace: argocd
spec:
destination:
namespace: mariadb
name: enterprise
project: default
sources:
# Values from Git
- repoURL: 'https://git.enterprise.com/enterprise/argocd'
targetRevision: HEAD
ref: values
# Chart from Chart Repo
- chart: /bitnamicharts/mariadb
repoUrl: registry-1.docker.io
targetRevision: 17.0.1
helm:
valueFiles:
- $values/enterprise/mariadb/values.yaml
syncPolicy:
automated:
prune: true
selfHeal: true
syncOptions:
- CreateNamespace=true
Step 3. Additionally I tried to add the repo manually by hopping onto the > argocd@argocd-server-b8bd4f4b5-b4tww:~$ argocd repo add oci://registry-1.docker.io/bitnamicharts --type helm --name stable --enable-oci --server 10.43.185.43
FATA[0000] Failed to establish connection to 10.43.185.43:443: dial tcp 10.43.185.43:443: connect: connection refusedAny assistance will be greatly appreciated. Thank you. |
Checklist:
argocd version.Describe the bug
When trying to declaratively deploy a repository that is prefixed with
oci://, argocd/helm can't pull the chart and errors with:There are also a few existing issues regarding OCI behaviour, however, I didn't find one that has the same error messages/error behaviour.
To Reproduce
Application spec that causes deployment errors:
Application spec that deploys and has no errors in argocd, but has application errors due to being only a demo chart:
The difference between the two specs seems to be the generated helm pull command, since manually running them errors the same way.
Failing pull command from application with
oci://prefix:Working pull command from application without
oci://prefix:Expected behavior
Adding/removing the
oci://prefix should not make a difference. Especially because the implicit definition is supported, while the explicit definition errors.Screenshots
Version
Logs
The text was updated successfully, but these errors were encountered: