A Helm chart for ArgoCD ApplicationSet services that uses pull request generator to automatically discover open pull requests within a repository with the label preview.
ApplicationSets interact with ArgoCD by creating, updating, managing, and deleting ArgoCD Applications. The job is to make sure that the ArgoCD Application remains consistent with the declared ApplicationSet resource(s). This can be thought of as sort of an “Application factory”. It takes an ApplicationSet and outputs one or more ArgoCD Applications.
This helm chart implements Pull Request generator of ApplicationSet, it uses API of an SCMaaS provider (GitHub and/or GitLab) to automatically discover open pull requests within an repository via GitHub / GitLab labels. This fits well with the style of building a test environment when you create a pull request.
Branch name(s) must be RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character
Full documentation: argocd-applicationsets-services.readthedocs.io.
Services that should already be installed and/or running.
- Kubernetes Cluster >= 1.31
- ArgoCD ApplicationSet Controller >= v2.13
- HELM >= v3.10
Use
repo:in values to inject or override values inkustomizeorhelm
helm repo add applicationsets-services https://saidsef.github.io/argocd-applicationsets-services/
helm repo update
helm upgrade --install pr-services applicationsets-services/argocd-applicationsets-services --namespace argocdThe pages below are the manual. Their sources are in docs/, and podman run --rm -v .:/docs docker.io/squidfunk/mkdocs-material:9 build renders the site into site/.
| Page | Contents |
|---|---|
| Overview | What the chart does, the feature set and the requirements |
| Architecture | What the chart renders, and how a pull request becomes a deployed environment |
| Configuration | Every value, its default, and the precedence between the global and per-provider keys |
| Repositories | The repos entries, the source shapes they select and worked examples |
| Deployment | Installing the chart, provisioning API tokens and scoping the AppProject |
| Testing | Rendering the chart locally, the lint and Kind jobs, and building the site |
| Troubleshooting | Symptoms, causes and fixes |
The chart values reference is generated from values.yaml into the chart README.
Our latest and greatest source of argocd-applicationsets-services can be found on GitHub. Fork us!
We would ❤️ you to contribute by making a pull request.
Please read the official Contribution Guide for more information on how you can contribute.