argo-cd | Declarative continuous deployment for Kubernetes | Continuous Deployment library

If I run git fetch origin and then git checkout on a series of consecutive commits, I get a relatively small repo directory.

But if I run git fetch origin and then git checkout FETCH_HEAD on the same series of commits, the directory is relatively bloated. Specifically, there seem to be a bunch of large packfiles.

The behavior appears the same whether the commits are all in place at the time of the first fetch or if they are committed immediately before each fetch.

The following examples use a public repo, so you can reproduce the behavior.

Why is the directory size of example 2 so much larger?

Example 1 (small):

I am trying to deploy ArgoCD and applications located in subfolders through Terraform in an AKS cluster.

This is my Folder structure tree:

I'm using app of apps approach, so first I will deploy ArgoCD (this will manage itself as well) and later ArgoCD will let me SYNC the cluster-addons and application manually once installed.

We have a full-blown setup using AWS EKS with Tekton installed and want to use ArgoCD for application deployment.

As the docs state we installed ArgoCD on EKS in GitHub Actions with:

I've started experimenting with Argocd as part of my cluster setup and set it up to watch a test repo containing some yaml files for a small application I wanted to use for the experiment. While getting to know the system a bit, I broke the repo connection and instead of fixing it I decided that I had what I wanted, and decided to do a clean install with the intention of configuring it towards my actual project.

I pressed the button in the web UI for deleting the application, which got stuck. After which I read that adding spec.syncPolicy.allowEmpty: true and removing the metadata.finalizers declaration from the application yaml file. This did not allow me to remove the application resource.

I then ran an uninstall command with the official manifests/install.yaml as an argument, which cleaned up most resources installed, but left the application resource and the namespace. Command: kubectl delete -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml

Have tried to use the kubectl delete application NAME --force flag and the --cascade=orphans flag on the application resource as well as on the argocd namespace itself. Now I have both of them stuck at terminating without getting any further.

Now I'm proper stuck as I can't reinstall the argocd in any way I know due to the resources and namespace being marked for deletion, and I'm at my wits end as to what else I can try in order to get rid of the dangling application resource.

Any and all suggestions as to what to look into is much appreciated.

I used the following command to install the Argo CD in the EKS fargate cluster.

From our Tekton pipeline we want to use ArgoCD CLI to do a argocd app create and argocd app sync dynamically based on the app that is build. We created a new user as described in the docs by adding a accounts.tekton: apiKey to the argocd-cm ConfigMap:

I have tried using a HELM chart repo for Apache via ArgoCD but it shows up degraded in the console but is in sync. I am using the Kubernetes cluster on docker desktop for Mac (M1 chip). Not quite sure what the issue is.

The helm chart details are:

I'm trying to install ArgoCD CLI on my windows 10 PC by following the command from the website substituting the version but receive the below error. It does not seem to like the + operator? Can anybody assist?

PS C:\Users\dell.docker> $url = "https://github.com/argoproj/argo-cd/releases/download/" + v2.2.3 + "/argocd-windows-amd64.exe"

I've installed ArgoCD on my kubernetes cluster using