ArgoCD
Deploy Argo CD in a DuploCloud-managed Infrastructure
Last updated
Was this helpful?
Deploy Argo CD in a DuploCloud-managed Infrastructure
Last updated
Was this helpful?
is a declarative, GitOps-based continuous delivery (CD) tool for Kubernetes. It enables you to manage Kubernetes resources using Git repositories as the source of truth, allowing you to automate and track application deployments with version control and auditing.
DuploCloud integrates with Argo CD, allowing you to deploy and manage applications declaratively within your Duplo-managed infrastructure. This integration streamlines continuous delivery workflows, reduces manual configuration, and helps enforce consistent deployments across environments.
Navigate to Administrator → Tenants and click Add to create a dedicated Tenant for hosting Argo CD, for example, argocd01.
Install Argo CD into your argocd01 Tenant using the official . This will deploy all necessary Argo CD components, including the API server, UI, and controllers, into the Kubernetes namespace for the Tenant.
Optionally, you can use DuploCloud’s if it's available in your environment.
Expose the Argo CD UI via an Ingress controller:
Ensure that a DNS name points to the ALB created by the Helm chart.
You can configure this manually or use if available.
To allow DuploCloud to authenticate with Argo CD:
Locate the argocd-cm ConfigMap.
Add the following entry:
This enables API key support for the admin account. No restart is required because Argo CD picks this up automatically.
Log into the Argo CD UI using the DNS name from above.
The default username is admin.
The initial password is in the Kubernetes secret named argocd-initial-admin-secret.
Navigate to Settings -> Accounts -> admin and generate a new token.
To enable DuploCloud to integrate with Argo CD, you'll need to add two custom system settings.
Navigate to Administrator → Settings → System Settings.
Click Add, The Add Config pane displays.
In the Config Type list box, select Other.
In the Other Config Type field, enter AppConfig/argocd.
In the Key field, enter the key (including INFRA_NAME):
For the endpoint: argocd/INFRA_NAME/endpoint.
For the token: argocd/INFRA_NAME/admin_token.
In the Value field, enter the corresponding value:
For the endpoint: https://DNS_NAME_FROM_STEP_4/.
For the token: Bearer TOKEN_FROM_STEP_5. Make sure the token value begins with Bearer. This prefix is required and not included in the token generated by Argo CD.
Go to CI/CD -> Argo CD in any Tenant within the INFRA_NAME infrastructure.
If everything is configured correctly, you will see synced applications.
If the token or endpoint are incorrect, you may see a "session" error.
To troubleshoot or interact directly:
You can list accounts: