How to fix repository not found in Kubernetes

Ensure the URL is correct and properly formatted:
- Git over HTTPS: https://github.com/owner/repo.git
- Git over SSH: [email protected]:owner/repo.git
- GitLab: https://gitlab.com/owner/repo.git
Test locally:

git clone <your-url>

Some Git providers require the .git suffix. For GitLab, explicitly add it:

https://gitlab.com/owner/repo.git

GitLab may send a 301 redirect without the suffix that ArgoCD does not follow.

If your application is a Helm chart, use the chart property instead of path in your Application:

apiVersion: argoproj.io/v1alpha1
kind: Application
spec:
  source:
    repoURL: https://helm.example.com
    chart: mychart
    targetRevision: 1.0.0

Instead of:

source:
    repoURL: https://helm.example.com
    path: mychart

For private GitHub repositories, the GitHub App must be authorized:
1. Go to your repository Settings > Installed GitHub Apps
2. Find the ArgoCD GitHub App
3. Click Authorize to grant repository access
4. Retry the repository connection in ArgoCD

Add repository credentials in ArgoCD before using a private repository:

argocd repo add https://github.com/private/repo \
  --username your-username \
  --password your-token

Check if ArgoCD can reach the repository host. From repo-server pod:

kubectl exec -it -n argocd deployment/argocd-repo-server -- \
  curl -I https://github.com/owner/repo

Verify that the path specified in your Application actually exists:

spec:
  source:
    path: k8s/overlays/prod

The directory must exist in the Git repository at that path.

Verify the repository can be accessed:

argocd repo test https://github.com/owner/repo

This will test if ArgoCD can connect to and access the repository.