Installing Argo CD with the community Helm chart
Deploying Argo CD from the argo-helm chart: what community maintained means for support, values for HA, SSO and ingress, CRD handling, and keeping chart and Argo CD versions aligned.
Argo CD installation and deployment
Installing and exposing Argo CD in your own infrastructure: manifests, Helm and Kustomize, ingress and TLS by controller, self-management and air-gapped clusters.
Installing Argo CD with Kustomize
Using the official manifests as a remote Kustomize base with patches: custom namespaces and the ClusterRoleBinding patch, configuration maps, and pinning versions.
Running Argo CD core without the API server or UI
Running headless Argo CD for cluster administrators who do not need multi-tenancy: what core-install.yaml leaves out, managing applications with kubectl and the CLI, and when to move to the full install.
Exposing Argo CD with NGINX ingress controllers
Publishing the Argo CD UI and gRPC CLI through NGINX: SSL passthrough versus TLS termination on the deprecated kubernetes/ingress-nginx, HTTP/2 and separate gRPC Ingress on F5 NGINX, and server.insecure.
Exposing Argo CD with Traefik
Routing Argo CD web and gRPC traffic through Traefik v3 with an IngressRoute: the h2c scheme for gRPC, a single host for both protocols, and TLS options.
Exposing Argo CD behind an AWS Application Load Balancer
Running Argo CD behind an ALB: the separate GRPC-protocol service and conditional routing for CLI traffic, TLS termination with server.insecure, and when classic ELBs or NLBs at layer 4 are simpler.
Exposing Argo CD with the Kubernetes Gateway API
Using HTTPRoute, GRPCRoute and TLSRoute to publish Argo CD as clusters move off Ingress: TLS termination versus passthrough and routing the CLI's gRPC traffic.
Serving Argo CD under a subpath with Istio
Publishing Argo CD at a path such as /argocd through an Istio Gateway and VirtualService: rootpath and basehref settings, proxy rewrites and the CLI's grpc-web root path.
TLS termination and certificates for Argo CD
Deciding where TLS ends in front of Argo CD: passthrough with one hostname, termination with separate gRPC and HTTPS hostnames, running the API server with server.insecure, and the CLI's grpc-web fallback.
Managing Argo CD with Argo CD
Putting Argo CD's own installation and configuration under GitOps: a Kustomize application over the base manifests, cluster and repository secrets as resources, the required ServerSideApply option, and safe bootstrapping.
Argo CD in air-gapped Kubernetes clusters
Running Argo CD with no internet access: mirroring the Argo CD images, internal Git, Helm and OCI registries, Dex connectors that need outbound calls, and patching without pulling from public sources.
