Fixing ArgoCD Progressing With Ingress
I now use ArgoCD for all my deployments in my level5 k8s cluster, but
because i am using a pureLB loadbalancer routed to traefik, argocd
normally got stucked in progressing state, this is how to solve it.
And it was found reading a this github issue
Which, in a nutshell you have to do so:
Edit the
argocd-cmconfigmapAdd resource.customizations block, like this
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35# Please edit the object below. Lines beginning with a '#' will be ignored,
# and an empty file will abort the edit. If an error occurs while saving this file will be
# reopened with the relevant failures.
#
apiVersion: v1
data:
application.instanceLabelKey: argocd.argoproj.io/instance
repositories: |
- type: helm
name: argo-cd
url: https://argoproj.github.io/argo-helm
resource.customizations: |
networking.k8s.io/Ingress:
health.lua: |
hs = {}
hs.status = "Healthy"
return hs
url: https://argocd.example.com
kind: ConfigMap
metadata:
annotations:
meta.helm.sh/release-name: argocd
meta.helm.sh/release-namespace: git
creationTimestamp: "2023-03-16T12:21:12Z"
labels:
app.kubernetes.io/component: server
app.kubernetes.io/instance: argocd
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/name: argocd-cm
app.kubernetes.io/part-of: argocd
helm.sh/chart: argo-cd-4.2.2
name: argocd-cm
namespace: git
resourceVersion: "53479139"
uid: 550eff19-512c-42f4-9e06-9f5df316221d
Done, your ArgoCD deploymentes wont be in progressing state anymore.
There are other fixes, that i will test soon, but at the moment, this is sufficient.