github.com/argoproj-labs/argocd-operator@v0.10.0/docs/usage/environment_variables.md (about)

     1  # Environment Variables
     2  
     3  The following environment variables are available in `argocd-operator`:
     4  
     5  | Environment Variable | Default Value | Description |
     6  | --- | --- | --- |
     7  | `CONTROLLER_CLUSTER_ROLE` | none | Administrators can configure a common cluster role for all the managed namespaces in role bindings for the Argo CD application controller with this environment variable. Note: If this environment variable contains custom roles, the Operator doesn't create the default admin role. Instead, it uses the existing custom role for all managed namespaces. |
     8  | `SERVER_CLUSTER_ROLE` | none | Administrators can configure a common cluster role for all the managed namespaces in role bindings for the Argo CD server with this environment variable. Note: If this environment variable contains custom roles, the Operator doesn’t create the default admin role. Instead, it uses the existing custom role for all managed namespaces. |
     9  | `REMOVE_MANAGED_BY_LABEL_ON_ARGOCD_DELETION` | false | When an Argo CD instance is deleted, namespaces managed by that instance (via the `argocd.argoproj.io/managed-by` label ) will retain the label by default. Users can change this behavior by setting the environment variable `REMOVE_MANAGED_BY_LABEL_ON_ARGOCD_DELETION` to `true` in the Subscription. |
    10  | `ARGOCD_LABEL_SELECTOR` | none | The label selector can be set on argocd-opertor by exporting `ARGOCD_LABEL_SELECTOR` (eg: `export ARGOCD_LABEL_SELECTOR=foo=bar`). The labels can be added to the argocd instances using the command `kubectl label argocd test1 foo=bar -n test-argocd`. This will enable the operator instance to be tailored to oversee only the corresponding ArgoCD instances having the matching label selector. |
    11  | `LOG_LEVEL` | info | This sets the logging level of the manager (operator) pod. Valid values are "debug", "info", "warn", "error", "panic" and "fatal". |
    12  
    13  Custom Environment Variables are supported in `applicationSet`, `controller`, `notifications`, `repo` and `server` components. For example:
    14  
    15  ```
    16  ...
    17  kind: ArgoCD
    18  metadata:
    19    name: argocd
    20    labels:
    21      example: controller
    22  spec:
    23    controller:
    24      resources: {}
    25      env:
    26        - name: FOO
    27          value: bar
    28  ...
    29  ```
    30  
    31  The following default value of images could be overridden by setting the environment variables:
    32  | Environment Variable | Default Value |
    33  | --- | --- |
    34  | `ARGOCD_IMAGE` | [quay.io/argoproj/argocd](quay.io/argoproj/argocd) |
    35  | `ARGOCD_REPOSERVER_IMAGE` | [quay.io/argoproj/argocd](quay.io/argoproj/argocd) |
    36  | `ARGOCD_DEX_IMAGE` | [ghcr.io/dexidp/dex](ghcr.io/dexidp/dex) |
    37  | `ARGOCD_KEYCLOAK_IMAGE` | [quay.io/keycloak/keycloak](quay.io/keycloak/keycloak) |
    38  | `ARGOCD_REDIS_IMAGE` | redis |
    39  | `ARGOCD_REDIS_HA_IMAGE` | redis |
    40  | `ARGOCD_REDIS_HA_PROXY_IMAGE` | haproxy |