Skip to content

Commit 5f8f600

Browse files
authored
Merge pull request #325 from bcgov/argocd-helm-update
Update Helm example for ArgoCD
2 parents adb1012 + c6fdf14 commit 5f8f600

File tree

1 file changed

+24
-17
lines changed

1 file changed

+24
-17
lines changed

src/docs/automation-and-resiliency/argo-cd-usage.md

Lines changed: 24 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -125,31 +125,38 @@ This document focuses on Helm and Kustomize.
125125

126126
#### Helm
127127

128-
If you're using [Helm](https://argo-cd.readthedocs.io/en/stable/user-guide/helm/), you may use your own package or a repository in the Docker Helm OCI repository.
128+
If you're using [Helm](https://argo-cd.readthedocs.io/en/stable/user-guide/helm/), you may use your own package or a chart repository in the Docker Helm OCI repository.
129129

130130
Start by creating a top-level directory dedicated to your application.
131131

132132
If using your own Helm package, place all of the Helm files within this directory, including your values file(s). When setting up the application in the Argo CD UI, you have the option to set a specific values file to use. For example, you may have a values file for each environment (dev, test, prod).
133133

134-
If using a package in the Docker Helm OCI repository (registry-1.docker.io), you will have to use the `docker-helm-oci-remote` caching repository in Artifactory, because your ArgoCD project only allows source repository URLs that match either your gitops repository or the Artifactory caching repository. To use Artifactory for this, create a Chart.yaml file in your application's directory in your gitops repository, setting the desired Helm package as a dependency. Here's an example that uses the bitnami redis-cluster package:
134+
If using a package in the Docker Helm OCI repository (registry-1.docker.io), you will have to use the `docker-helm-oci-remote` caching repository in Artifactory, because your ArgoCD project only allows source repository URLs that match either your gitops repository or the Artifactory caching repository. To use Artifactory for this, create an ArgoCD App using the following guidelines:
135135

136-
```
137-
apiVersion: v2
138-
name: redis-cluster
139-
type: application
140-
version: "11.5.2"
141-
appVersion: "7.4.2"
142-
dependencies:
143-
- name: redis-cluster
144-
version: "11.5.2"
145-
repository: "oci://artifacts.developer.gov.bc.ca/docker-helm-oci-remote/bitnamicharts"
146-
```
147-
148-
To apply local customizations, copy the values.yaml file from the original repository into this same directory, make your modifications, and select that file in the values file list in the ArgoCD configuration.
136+
* Source repository URL: `artifacts.developer.gov.bc.ca/docker-helm-oci-remote`
137+
* Source repository type: `HELM`
138+
* Chart name: Enter as group/project, such as `bitnamicharts/mariadb`
139+
* Chart version: In the field adjacent to the chart name, enter the version number, such as `20.2.0`
140+
* Helm settings: Select a Values file or enter individual values
149141

142+
To create an ArgoCD App using a manifest, use the following example as a guide.
150143
```
151-
Chart.yaml
152-
values.yaml
144+
apiVersion: argoproj.io/v1alpha1
145+
kind: Application
146+
metadata:
147+
name: mariadb
148+
spec:
149+
destination:
150+
namespace: abc123-dev
151+
server: https://kubernetes.default.svc
152+
project: abc123
153+
source:
154+
chart: bitnamicharts/mariadb
155+
helm:
156+
valueFiles:
157+
- charts/common/values.yaml
158+
repoURL: artifacts.developer.gov.bc.ca/docker-helm-oci-remote
159+
targetRevision: 20.2.0
153160
```
154161

155162
#### Kustomize

0 commit comments

Comments
 (0)