marco/veda
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity
9ccce95b25
veda/platform/components/02-argocd
History
Marco van Zijl 27aecf6e78 Refactor ArgoCD HTTPRoute configuration and update sync policy for automated management
2025-11-08 15:33:54 +01:00
..
post-install Refactor ArgoCD HTTPRoute configuration and update sync policy for automated management 2025-11-08 15:33:54 +01:00
install.sh Big rewrite for clean app-of-apps setup 2025-11-08 13:38:36 +01:00
readme.md Big rewrite for clean app-of-apps setup 2025-11-08 13:38:36 +01:00
values.yaml Add gateway-api application and update Traefik configuration; disable old ingress 2025-11-08 14:51:38 +01:00

readme.md

ArgoCD Component

Overview

ArgoCD is our GitOps continuous delivery tool for Kubernetes.

Configuration

The following configurations are available:

  • Domain: argocd.noxxos.nl
  • Ingress: Enabled with Traefik
  • Version: 9.1.0

Post-Install

After installation:

  1. The admin password will be displayed

  2. Initial access is available through port-forward:

    kubectl port-forward svc/argocd-server -n argocd 8080:443

    Then visit: https://localhost:8080

  3. Once Traefik is running, access through ingress will be available

Dependencies

  • Kubernetes cluster
  • Helm v3+
  • Traefik (for ingress)

Troubleshooting

If you can't access ArgoCD:

  1. Check if the pods are running:

    kubectl get pods -n argocd

  2. Check ingress status

    kubectl get ingress -n argocd