argoproj / argoproj/argo-cd

Not able to add helm enable OCI Private repo through Argocd GUI as well as through command line

Open
#19,086 5 comments 0 reactions 0 assignees View on GitHub
bug more-information-needed
Dominant language
Go
Stars
24.2k
Forks
7.8k
Avg merge
1d 11h
Merged PRs (30d)
233

Description

Not able to add helm enable OCI Private repo through Argocd GUI as well as through command line using below cmd. I have checled the correct certificate is in place.

argocd repo add registry-rat.xyz.com --type helm --name reponame --enable-oci --username 'XYZ' --password 'XYZ ==> Failed

I am able to add Private repo through argocd command by passing Flag --insecure-skip-server-verification but App deployment failed using this repo with below error

argocd repo add registry-rat.xyz.com --type helm --name reponame --enable-oci --username 'XYZ' --password 'XYZ' --insecure-skip-server-verification

ERROR

Unable to create application: application spec for reponame is invalid: InvalidSpecError: repository not accessible: repositories not accessible: &Repository{Repo: "registry-rat.xyz.com", Type: "helm", Name: "oci", Project: ""}: repo client error while testing repository: rpc error: code = Unknown desc = error testing repository connectivity: helm registry login registry-rat.xyz.com --username ****** --password ****** --insecure failed exit status 1: WARNING: Using --password ****** the CLI is insecure. Use --password-stdin. Error: Get "
https://registry-rat.xyz.com/v2/":
unauthorized: authentication required

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the shown `argocd repo add` commands and the application validation error, checking the distinction between certificate verification and registry authentication. Trace the repository connectivity and Helm OCI login entry points. Done means a private OCI Helm repository can be added without the insecure verification flag and an application using it validates successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
helm, kubernetes
Domain
ci-cd, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.