From a3295a348d89d800ed657d455172801f2b3ad3c0 Mon Sep 17 00:00:00 2001 From: sujiba Date: Sun, 11 May 2025 18:04:47 +0200 Subject: [PATCH] feat: added argocd --- talos/README.md | 25 ++++++++++++++++++++++--- 1 file changed, 22 insertions(+), 3 deletions(-) diff --git a/talos/README.md b/talos/README.md index 8556cf5..8ed401c 100644 --- a/talos/README.md +++ b/talos/README.md @@ -12,7 +12,8 @@ - [Talos image factory](#talos-image-factory) - [Boot Image](#boot-image) - [Cluster bootstrap](#cluster-bootstrap) -- [Cilium CNI](#cilium-cni) + - [Cilium CNI](#cilium-cni) + - [ArgoCD](#argocd) # Required packages ```bash @@ -103,7 +104,7 @@ talosctl apply-config --insecure -n 10.10.10.3 --file clusterconfig/home-cluster talosctl bootstrap -n 10.10.10.3 -e 10.10.10.3 --talosconfig talosconfig ``` -# Cilium CNI +## Cilium CNI After applying the machine config and bootstrapping Talos will appear to hang on phase 18/19 with the message: retrying error: node not ready. This happens because nodes in Kubernetes are only marked as ready once the CNI is up. As there is no CNI defined, the boot process is pending and will reboot the node to retry after 10 minutes, this is expected behavior. During this window you can install Cilium manually by running the following: @@ -132,4 +133,22 @@ helm install \ # Enable and disable hubble cilium hubble enable --ui cilium hubble disable -``` \ No newline at end of file +``` + +## ArgoCD +Create argocd namespace and install the application + ```bash + kubectl create ns argocd + kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml +``` + +Port forward the web interface of argocd and get the initial login password +```bash +kubectl port-forward svc/argocd-server -n argocd 8080:443 +kubectl get secret argocd-initial-admin-secret -n argocd -o jsonpath='{.data}' +``` + +Open your browser and go to `https://localhost:8080`. Log in with `admin` and the `argocd-initial-admin-secret`. Click on User-Info -> Update Password and change the password. You can then delete the secret. +```bash +kubectl delete secret argocd-initial-admin-secret -n argocd +```