Open Brawdunoir opened 8 months ago
@Brawdunoir Try adding the environment variables to your argo-cd repo-server environment. This is how I have accomplished this to auth to private ECR registry containing OCI Helm charts with helmfile.
# argo-cd helm chart values
repoServer:
envFrom:
- secretRef:
name: argocd-helmfile-oci-auth # Created secret with environment vars of auth.
# example secret
apiVersion: v1
kind: Secret
metadata:
name: argocd-helmfile-oci-auth
namespace: argocd
data:
HARBOR_PASSWORD: <your token for auth>
HARBOR_USERNAME: <your user for auth>
type: Opaque
Hello, I ran into an issue using your plugin when dealing with OCI private helm registries.
Context
I want to add an ArgoCD application that pull a repo containing a
helmfile.yaml
.Within this
helmfile.yaml
I got some OCI private repositories I need to authenticate first before being able to pull.I tried a few things that are not working:
helmfile-plugin
sidecar usinghelm registry login
HARBOR_USERNAME
andHARBOR_PASSWORD
environment variables in the ArgoCD application directly (as per helmfile documentation)Problem
I got a
401 Unauthorized
response when fetching a private helm repository.It tries to connect as an anonymous user in order to pull the chart (Harbor logs).
Current solution
Make the OCI registry public solves the issue in the meantime, the app can be deployed without any issue.
This is not a long term solution for me because sometimes we host docker repositories along helm ones and these cannot be public.
Configuration
Logs
Thanks for your awesome work on this plugin !
PS: If we cannot use private helm repos using this plugin, imo it should be stated in the
README.md
.