Argo CD: Up and Running

Chapter 3. Interacting with Argo CD

Argo CD includes a fully declarative configuration model which supports a hands-off approach to GitOps and the management of a GitOps server. However, in some cases, more direct methods will be needed for interacting with the Argo CD server. In the previous chapter, we covered the Argo CD UI, which is one method for interacting with the platform as it provides a visual approach to the current state of GitOps. While the UI may be one of the most common methods for utilizing Argo CD, there are additional mechanisms to choose from, including a fully functional CLI and RESTful API. This chapter builds on the foundational concepts established in Chapter 2 for accessing and configuring Argo CD along with introducing several additional approaches that can be employed depending on the use case or preference.

The User Interface in Depth

In Chapter 2, the UI was used as a way to access Argo CD. However, when deployed to the kind cluster, it required establishing a connection to the server component using the kubectl port-forward command. While this was acceptable for initial testing and validation, it is by no means how one should utilize a service long term. A more robust approach should be undertaken to provide a more reliable exposure of services.

One of the most common methods for exposing services and gaining access to resources within a Kubernetes cluster is to leverage an Ingress resource. An Ingress provides a means for exposing services outside ...