github.com/argoproj/argo-cd/v2@v2.10.9/docs/operator-manual/installation.md (about)

     1  # Installation
     2  
     3  Argo CD has two type of installations: multi-tenant and core.
     4  
     5  ## Multi-Tenant
     6  
     7  The multi-tenant installation is the most common way to install Argo CD. This type of installation is typically used to service multiple application developer teams
     8  in the organization and maintained by a platform team.
     9  
    10  The end-users can access Argo CD via the API server using the Web UI or `argocd` CLI. The `argocd` CLI has to be configured using `argocd login <server-host>` command
    11  (learn more [here](../user-guide/commands/argocd_login.md)).
    12  
    13  Two types of installation manifests are provided:
    14  
    15  ### Non High Availability:
    16  
    17  Not recommended for production use. This type of installation is typically used during evaluation period for demonstrations and testing.
    18  
    19  * [install.yaml](https://github.com/argoproj/argo-cd/blob/master/manifests/install.yaml) - Standard Argo CD installation with cluster-admin access. Use this
    20    manifest set if you plan to use Argo CD to deploy applications in the same cluster that Argo CD runs
    21    in (i.e. kubernetes.svc.default). It will still be able to deploy to external clusters with inputted
    22    credentials.
    23  
    24  * [namespace-install.yaml](https://github.com/argoproj/argo-cd/blob/master/manifests/namespace-install.yaml) - Installation of Argo CD which requires only
    25    namespace level privileges (does not need cluster roles). Use this manifest set if you do not
    26    need Argo CD to deploy applications in the same cluster that Argo CD runs in, and will rely solely
    27    on inputted cluster credentials. An example of using this set of manifests is if you run several
    28    Argo CD instances for different teams, where each instance will be deploying applications to
    29    external clusters. It will still be possible to deploy to the same cluster (kubernetes.svc.default)
    30    with inputted credentials (i.e. `argocd cluster add <CONTEXT> --in-cluster --namespace <YOUR NAMESPACE>`).
    31  
    32    > Note: Argo CD CRDs are not included into [namespace-install.yaml](https://github.com/argoproj/argo-cd/blob/master/manifests/namespace-install.yaml).
    33    > and have to be installed separately. The CRD manifests are located in the [manifests/crds](https://github.com/argoproj/argo-cd/blob/master/manifests/crds) directory.
    34    > Use the following command to install them:
    35    > ```
    36    > kubectl apply -k https://github.com/argoproj/argo-cd/manifests/crds\?ref\=stable
    37    > ```
    38  
    39  ### High Availability:
    40  
    41  High Availability installation is recommended for production use. This bundle includes the same components but tuned for high availability and resiliency.
    42  
    43  * [ha/install.yaml](https://github.com/argoproj/argo-cd/blob/master/manifests/ha/install.yaml) - the same as install.yaml but with multiple replicas for
    44    supported components.
    45  
    46  * [ha/namespace-install.yaml](https://github.com/argoproj/argo-cd/blob/master/manifests/ha/namespace-install.yaml) - the same as namespace-install.yaml but
    47    with multiple replicas for supported components.
    48  
    49  ## Core
    50  
    51  The Argo CD Core installation is primarily used to deploy Argo CD in
    52  headless mode. This type of installation is most suitable for cluster
    53  administrators who independently use Argo CD and don't need
    54  multi-tenancy features. This installation includes fewer components
    55  and is easier to setup. The bundle does not include the API server or
    56  UI, and installs the lightweight (non-HA) version of each component.
    57  
    58  Installation manifest is available at [core-install.yaml](https://github.com/argoproj/argo-cd/blob/master/manifests/core-install.yaml).
    59  
    60  For more details about Argo CD Core please refer to the [official
    61  documentation](./core.md)
    62  
    63  ## Kustomize
    64  
    65  The Argo CD manifests can also be installed using Kustomize. It is recommended to include the manifest as a remote resource and apply additional customizations
    66  using Kustomize patches.
    67  
    68  
    69  ```yaml
    70  apiVersion: kustomize.config.k8s.io/v1beta1
    71  kind: Kustomization
    72  
    73  namespace: argocd
    74  resources:
    75  - https://raw.githubusercontent.com/argoproj/argo-cd/v2.7.2/manifests/install.yaml
    76  ```
    77  
    78  For an example of this, see the [kustomization.yaml](https://github.com/argoproj/argoproj-deployments/blob/master/argocd/kustomization.yaml)
    79  used to deploy the [Argoproj CI/CD infrastructure](https://github.com/argoproj/argoproj-deployments#argoproj-deployments).
    80  
    81  ## Helm
    82  
    83  The Argo CD can be installed using [Helm](https://helm.sh/). The Helm chart is currently community maintained and available at
    84  [argo-helm/charts/argo-cd](https://github.com/argoproj/argo-helm/tree/main/charts/argo-cd).
    85  
    86  ## Supported versions
    87  
    88  For detailed information regarding Argo CD's version support policy, please refer to the [Release Process and Cadence documentation](https://argo-cd.readthedocs.io/en/stable/developer-guide/release-process-and-cadence/).
    89  
    90  ## Tested versions
    91  
    92  The following table shows the versions of Kubernetes that are tested with each version of Argo CD.
    93  
    94  {!docs/operator-manual/tested-kubernetes-versions.md!}