Argo CD.

src/017_installing_argo_cd.md → src/017_installing_argocd.md

@@ -2,18 +2,24 @@
 
 Argo CD is a large, complicated application in its own right; its Helm chart is thousands of lines long. I'm not trying to learn it all right now, and fortunately, I have a fairly simple structure in mind; build out our applications with an app-of-apps pattern from a public git repository hosted on GitHub. That's about as vanilla as it gets.
 
-I'll install Argo CD via a new Ansible [playbook](https://github.com/goldentooth/cluster/blob/main/playbooks/install_argo_cd.yaml) and [role](https://github.com/goldentooth/cluster/tree/main/roles/goldentooth.install_argo_cd).
+I'll install Argo CD via a new Ansible [playbook](https://github.com/goldentooth/cluster/blob/main/playbooks/install_argocd.yaml) and [role](https://github.com/goldentooth/cluster/tree/main/roles/goldentooth.install_argocd).
 
 None of this is particularly complex, but I'll document some of my values overrides here:
 
 ```yaml
 # I've seen a mix of `argocd` and `argo-cd` scattered around. I preferred
 # `argocd`, but I will shift to `argo-cd` where possible to improve
 # consistency.
-nameOverride: 'argo-cd'
+#
+# EDIT: The `argocd` CLI tool appears to be broken and does not allow me to
+# override the names of certain components when port forwarding.
+# See https://github.com/argoproj/argo-cd/issues/16266 for details.
+# As a result, I've gone through and reverted my changes to standardize as much
+# as possible on `argocd`.
+nameOverride: 'argocd'
 global:
-  # This evaluates to `argo-cd.goldentooth.hellholt.net`.
-  domain: "{{ argo_cd_domain }}"
+  # This evaluates to `argocd.goldentooth.hellholt.net`.
+  domain: "{{ argocd_domain }}"
   # Add Prometheus scrape annotations to all metrics services. This can
   # be used as an alternative to the ServiceMonitors.
   addPrometheusAnnotations: true
@@ -38,7 +44,7 @@ configs:
       type: 'git'
       name: 'gitops'
       # This turns out to be https://github.com/goldentooth/gitops.git
-      url: "{{ argo_cd_app_repo_url }}"
+      url: "{{ argocd_app_repo_url }}"
 
 redis-ha:
   # Enable Redis high availability.
@@ -72,7 +78,7 @@ applicationSet:
 
 ![Pods in the Argo CD namespace](./images/argo_cd_pods.png)
 
-After running `kubectl -n argo-cd port-forward service/argo-cd-server 8081:443 --address 0.0.0.0` on one of my control plane nodes, I'm able to view the web interface, log in, and see that the repository is connectable but that there's nothing interesting in it.
+After running `kubectl -n argocd port-forward service/argocd-server 8081:443 --address 0.0.0.0` on one of my control plane nodes, I'm able to view the web interface, log in, and see that the repository is connectable but that there's nothing interesting in it.
 
 ![Argo CD web interface](./images/argo_cd.png)
 

src/SUMMARY.md

@@ -16,4 +16,4 @@
 - [Admitting the Worker Nodes](./014_bootstrapping_3.md)
 - [Where Do We Go From Here?](./015_where_do_we_go_from_here.md)
 - [Installing Helm](./016_installing_helm.md)
-- [Installing Argo CD](./017_installing_argo_cd.md)
+- [Installing Argo CD](./017_installing_argocd.md)