Complete the steps for setting up the ArgoCD tool to support integration with Artifactory as a Helm repository
ArgoCD is the Developer Environment’s continuous delivery tool. Before you can use it as part of the environment, it must first be configured.
Before setting up ArgoCD, set up Artifactory so that ArgoCD can use it as a Helm repository.
Configure ArgoCD to use Artifactory as a Helm repository.
The ArgoCD repository contains files and samples for configuring ArgoCD.
Clone the repository to your development machinegit clone firstname.lastname@example.org:IBM/template-argocd-gitops.gitcd template-argocd-gitops
The Helm repository is in Artifactory. ArgoCD will need the URL to that repository.
In the Artifactory console, select the Home page
In the Set Me Up section, click on the
In the Set Me Up dialog for the generic-local repository, copy the Deploy URL
The repo you cloned contains an ArgoCD configuration file. Put the Helm repository location in that file and deploy it to your Developer Environment.
Log into your cluster from the CLI
Add the folder name for your helm artifacts to the URL copied from the Artifactory console
[artifact-helm -repository -location]/[helm artifact folder]this is often the same name as your resource group
In your local copy of the
./config /addhelmrepository.sh [artifact-helm-repository-location]/[helm artifact folder]where `[artifact-helm-repository-location]` is the URL of the Helm repository location in Artifactory
Verify that the new configuration has deployed
In the Kubernetes dashboard or OpenShift console, navigate to the Config Maps in the
argocd-cmconfig map and confirm that its
helm.repositoriesproperty specifies the Artifactory URL
ArgoCD now has the configuration file in the Developer Environment that it needs to access the Helm chart repository in Artifactory.