GitOps the Hard Way, with Argo CD

Argo CD Configuration

Argo CD exposes a large number of configuration settings. There are two common ways to customize an installation. If you want to keep the official manifests you just applied and only change a few things, such as the namespace, image versions, or replica counts, Kustomize is the recommended approach: you reference the upstream install.yaml as a remote resource and layer patches on top of it. If you would rather manage Argo CD as a packaged release, you can install it with Helm instead, using a values.yaml file to drive the configuration. Note that the Argo CD Helm chart is community maintained rather than published by the Argo CD project itself.

For example, with the Helm chart, you can customize the installation to fit your needs using the values.yaml file. Below, we disable the local Redis instance because we have an external one, set the number of replicas for the application controller to 2 and configure it to use the external Redis, enable autoscaling for the repo server, configure the repo server and the API server to use the same external Redis, and enable debug logging:

# Disable the internal Redis server
redis:
  enabled: false

# Set the number of replicas for the application controller to 2
# and configure it to use an external Redis server
controller:
  replicas: 2
  extraArgs:
    - --redis=hostname:6379
    - --redisdb=1

# Enable autoscaling for the repo server
# and configure it to use the same external Redis
repoServer:
  autoscaling:
    enabled: true
    minReplicas: 2
  extraArgs:
    - --redis=hostname:6379
    - --redisdb=1

# Configure the Server to use the same external Redis
server: