|
06c774ad3c
|
add statusbadge to argo
|
2024-02-20 20:58:52 +01:00 |
|
|
f0aa03a2d5
|
fix argocd
|
2024-02-18 14:14:02 +01:00 |
|
|
55382ae3dc
|
fix argo ingress
|
2024-02-18 14:07:22 +01:00 |
|
|
8f15467a36
|
try to fix 3
|
2024-02-18 06:59:06 +01:00 |
|
|
c696104e0c
|
try to fix argocd configmap
|
2023-10-23 17:15:26 +02:00 |
|
|
93b8c785a1
|
add the ingress class to the ingresses to improve compatibility in the early stages of the cluster creation, where the default class is not yet propagated.
|
2023-06-19 07:15:19 +02:00 |
|
|
c22ebeb2f2
|
change host domain for argo
|
2023-06-19 07:02:22 +02:00 |
|
|
115c128c60
|
further trim down the ingress ressource to the bare minimum
|
2023-06-19 00:50:20 +02:00 |
|
|
82294d3cf5
|
fck nginx-ingress, use loadbalancer for https
|
2023-06-18 05:18:02 +02:00 |
|
|
6efe28a8ef
|
add configmap for argocd
|
2023-04-23 05:57:57 +02:00 |
|
|
2aa3e076fe
|
fix argocd ingress ressource
|
2023-03-12 23:21:52 +01:00 |
|
|
230a20273c
|
fix https backend for svc/argocd-server
|
2023-02-12 21:22:56 +01:00 |
|
|
fd60c22347
|
fix port for argo ingress
|
2023-02-12 20:45:25 +01:00 |
|
|
1af67a038c
|
fixes to argo configs
|
2023-02-12 20:43:01 +01:00 |
|
|
992f7060ba
|
add argocd
|
2023-02-12 20:36:55 +01:00 |
|