Runtime prerequisites

Complete the prerequisites depending on your installation mode

Before installing GitOps Runtimes, ensure you meet the system requirements, and complete the necessary prerequisites, which vary by installation mode.

Prerequisites summary

This table lists the prerequisites for installing a GitOps Runtime, depending on the installation mode.

Prerequisite Runtime with existing Argo CD Runtime with new Argo CD
Remove Argo Project and SealedSecret components ✅ ✅
Configure connectivity with Argo CD services ✅ -
Verify Argo CD root path configuration ✅ -

Remove Argo Project and SealedSecret components

For GitOps Runtime installation, the target cluster should not have:

  • SealedSecret controller components
  • For an existing Argo CD instance:
    • Argo Events
    • Argo Rollouts
    • Argo Workflows
  • For a new Argo CD instance:
    • Argo CD
    • Argo Events
    • Argo Rollouts
    • Argo Workflows

Configure connectivity with Argo CD services (Existing Argo only)

Installing the GitOps Runtime with an existing Argo CD instance requires connectivity between the Runtime and key Argo CD services. The following Argo CD services must be accessible from the GitOps Runtime: argocd-server argocd-repo-server argocd-redis

There are two options to configure service discovery:

  • Auto-detection via labels
  • Configuring service names and ports in the Runtime’s values.yaml file.

Configure auto-detect for Argo CD services

Assign the correct labels to the Argo CD services for the GitOps Runtime to auto-detect them.

  • argocd-server: app.kubernetes.io/component=server,app.kubernetes.io/part-of=argocd
  • argocd-repo-server: app.kubernetes.io/component=repo-server,app.kubernetes.io/part-of=argocd
  • argocd-redis: app.kubernetes.io/component=redis,app.kubernetes.io/part-of=argocd

Manually configure service names and ports in values.yaml

If auto-detection is not feasible, configure the names and ports for each of the Argo CD services in the Runtime’s values.yaml file located here.

Here’s an example of the service configuration in values.yaml.

global:
  external-argo-cd:
    server:
      svc: argocd
      port: 80
    redis:
      svc: argocd-redis
      port: 6379
    repoServer:
      svc: argocd-repo-server
      port: 8081
...

Verify Argo CD root path configuration (Existing Argo only)

If your existing Argo CD instance runs behind a reverse proxy and uses a non-default root path, you must configure the path in the Runtime’s values.yaml in global.external-argo-cd.server.rootpath.

Here’s an example of the non-default root path configuration for Argo CD in values.yaml.

global:
  external-argo-cd:
    server:
      svc: argocd
      port: 80
      rootpath: '/argocd' # example value if ArgoCD is behind a reverse proxy such as https://example.com/argocd/
...

GitOps Runtimes with ingress controllers/service meshes
Ingress configuration for Runtimes
Install GitOps Runtime with existing Argo CD
Install GitOps Runtime with new Argo CD