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
Confirmed that argo-cd-argocd-repo-server is able to access argo-server-sso from kubernetes Secret
argocd@argo-cd-argocd-repo-server-6644b58d8f-rqf69:~$ kubectl get Secret argo-server-sso
NAME TYPE DATA AGE
argo-server-sso Opaque 5 103d
Issue
When I try to create ArgoCD app with provided helmfile repository, it's throwing following error.
Unable to create application: application spec for delete is invalid: InvalidSpecError:
Unable to generate manifests in sample-app: rpc error: code = Unknown desc = plugin sidecar failed.
error generating manifests in cmp: rpc error: code = Unknown desc = error generating manifests: `argo-cd-helmfile.sh init` failed exit status 1: helm version v3.14.2+gc309b6f helmfile version 0.162.0
starting init vals-k8s: Unable to get a valid kubeConfig path: No path was found in any of the following: kubeContext URI param, KUBECONFIG environment variable, or default path /tmp/__argo-cd-helmfile.sh__/apps/delete/.kube/config does not exist.
vals-k8s: Unable to get a valid kubeConfig path: No path was found in any of the following: kubeContext URI param, KUBECONFIG environment variable, or default path /tmp/__argo-cd-helmfile.sh__/apps/delete/.kube/config does not exist. in ./helmfile.yaml:
error during helmfile.yaml.part.0 parsing: template: stringTemplate:3:10: executing "stringTemplate" at <fetchSecretValue (.StateValues | get "C3SP_HELM_REPO_URL" "secretref+k8s://v1/Secret/argo/argo-server-sso/helm-repo-url")>: error calling fetchSecretValue: expand k8s://v1/Secret/argo/argo-server-sso/helm-repo-url:
No path was found in any of the following: kubeContext URI param, KUBECONFIG environment variable, or default path /tmp/__argo-cd-helmfile.sh__/apps/delete/.kube/config does not exist.
That’s a good use case. I am not sure why it wouldn’t try and build a kubeconfig from the service account files but it likely would be pretty easy to get around that.
If you exec directly to the container and issue a kubectl command to fetch the secret does that work?
Environment:
Private Repository in Helmfile.yaml
ArgoCD Setup
Confirmed that
argo-cd-argocd-repo-server
is able to accessargo-server-sso
from kubernetes SecretIssue
When I try to create ArgoCD app with provided helmfile repository, it's throwing following error.
Reference: Vals Kubernetes
The text was updated successfully, but these errors were encountered: