* feat: update subchart minio and add Helm 3 compatibility Argo WF
Signed-off-by: Carlos Juan Gómez Peñalver <carlosjuangp@gmail.com>
* fix: use Helm 2 to create the dependencies.lock helm/helm#7233
Fix related to this ticket merged 8h ago
https://github.com/helm/helm/issues/7233
Signed-off-by: Carlos Juan Gómez Peñalver <carlosjuangp@gmail.com>
* fix: revert testing values
Signed-off-by: Carlos Juan Gómez Peñalver <carlosjuangp@gmail.com>
The official Argo-CD HA manifests do not scale the dex server
or the application controller past 1 because they still have
local caches and cannot support more than one pod at a time
Signed-off-by: Carson Anderson <ca@carsonoid.net>
* added crds directory for helm 3 compability
* added eventsource-crd for helm2
* updated image tags to newer version, added new property for additionalRules for compability
* updated SA Rules to match installation yaml from events repo
* introduced shortnames to match upstream crds
* updated env var names to match events installation yml from upstream repo
* updated chart and app version
Automatically setting password modification time to the current time leads to
it changing every time the chart is rendered. Ironically, this is a problem
when Argo CD manages itself using this chart ;-)
This spec.subdomain field is not part of OpenShift 3.11 route OpenAPI
specification and since it's empty it can safely be removed without impacting
OpenShift 4.
* Fixes version label in argocd components
Breaking change introduced in this PR https://github.com/argoproj/argo-helm/pull/203 causes labeles to be removed due to an empty vaule in .Values.*.image.tag.
* Update Chart.yaml
patch version bump
* fix: Update Argo icon URL for the Helm charts
The path to the argo.png image has changed in
the Argo repository.
The helm charts icon URL still points to the
old URL which is invalid. The image has moved
from /argo.png to /docs/assets/argo.png.
* chore: bump argocd chart version
* Upgrade to v1.3.6
Signed-off-by: David J. M. Karlsen <david@davidkarlsen.com>
* bump version
Signed-off-by: David J. M. Karlsen <david@davidkarlsen.com>
* [argo-cd] Added simple PrometheusRule
This patch adds a few simple rules which you can leverage to make
sure that your infrastructure is up to date. They are optional
and opt-in only.
* Add conditional selector fix from #180
* Bump chart version
Signed-off-by: Léo Depriester <leo.depriester@camptocamp.com>
* Fix controller env path
* Updating chart bump to patch as this is a backwards compatible change
* ArgoCD: Configure Repository Credentials in Values
* Argo CD Helm Chart: Add a Secret Resource in Repo Server for configuring Repository Credentials
Change-Id: I64c343d3558a939d0faef795e62d4e258810bc67
* Minor formatting fix, add documentation.
* [charts/argo-cd] Update to 1.3, some chart cleanup
* Bumps the version of ArgoCD to 1.3 and the chart version to 1.2 due
to a CRD change. Restored conditional CRDs to correct #27. Additionally,
some value defaults were added so Helm strict linting could pass.
* This adds some examples to the values.yaml on how to use the new
Helm repo chart types. Add helmignore to help with development.
* Added Role and service account to repo-server
* Fixed comment in repo-server SA name helper
* Bumped chart version
* Added repoServer service account annotations
* Updating for events 0.11
* Adding note to the README about how to install CRDs from github
* Fixing handling of serviceAccount variable inside of loops
* Better Helm chart NOTES.txt templating
Add some extra templating to NOTES.txt, which are displayed to the
user after a successful helm install command. These are really
helpful notes, but if you didn't specify a release name of argocd
or put it in a separate namespace, these commands weren't exactly
working with a copy paste. Now they should take into account
the release name and release namespace helm was given.
* Small CONTRIBUTING.md command line change
Instead of just doing `argocd version`, be a little more explicit
by passing in the server name and insecure flag. This will make
sure that you're doing the version of the instance you're
port-forwarding above, as opposed to some other argocd.
The argocd application expects that the label 'app.kubernetes.io/part-of' is set to 'argocd' otherwise the configmap or secret is rejected, and the argocd-dex-server, argocd-server, and argocd-application-controller fail to start.
This updates the Helm linting system with the following changes:
- Import lintconf.yaml with small change to comment distance in order to
match existing values.yaml standards
- Update Chart.yaml and values.yaml in each chart to pass linting
standards
- Maintainers added to each chart from OWNERS + CODEOWNERS, the linter
requires GitHub usernames so argo-events maintainer names were converted
- README updated with documentation around chart standards and testing
- A local shell script added for running lint tests locally
* Updating chart to 2.4.1
Adding a helm flag instead of --no-hooks for sustainability
Add better readme around CRDs
Fixing controller clusterrole
adding workflowtemplate to argo-ui clusterrole
* Bumping to newest patch
* Bumping to newest patch 2.4.2
This adds new parameters to each Deployment in the argo-cd chart,
allowing users to specify custom volumes to mount. This makes it
possible to use a Git repository self-signed certificates by manually
adding a "known_hosts" file, as recommended in the documentation:
https://argoproj.github.io/argo-cd/user-guide/private-repositories/
"volumes" and "volumeMounts" parameters are added to each Deployment,
with defaults set to empty.
This change was tested by templating the chart with default parameters,
and by templating it with volume mounts specified for each service.
* Add application controller resources
First chart version for argo-cd
added the new labels recommeneded for k8
* Add repo server resources
Use legacy label and new one for application controller selectors
Set labels for deployment for easier discovery
* Configure git repositories, helm chart museums and dex connectors
This way argo-cd could be configured to update itself via helm
* Parameterize the rbac configmap
* Parameterize webhook secrets
* Parameterize server deployment and set services with the labels
* Add service account, role and rolebinding for server deployment
* Clean the old label, use only latest recommendations
Follow the ideas and changes of https://github.com/argoproj/argo-cd/pull/1035
* Fix var naming issues
* Fix server service incorrect ports
* Install crds with helm hook
* Enable cluster admin accessby default
Default installation will allow installing apps in the current cluster without
inputted credentials. For other clusters inputted credentials will be needed
* Parameterize the dex server
* Harcode resource names because code expects them this way
Some resource names and application urls are hardcoded in code with these
names. So they can't be parameterized.
* Create the ingress with tls passthrough support
Tls is terminated on the ArgoCD server, not on ingress
* Fix typo on application controller sa
* Add notes on how to connect to server UI after installation
* Chart Grooming
- Changed the default `workflow-controller` installation to use the `ServiceAccount` that is created and bound.
- Customized the instanceID logic:
- No longer defaults to installed (this was very difficult to see/understand when coming from starter tutorials)
- Kept logic to allow for release name or explicit mappings but changed structure a bit
- Added in optional configuration for:
- CRD Install hook's ServiceAccount to allow clean install if your
default roles aren't privledged
- Optional Pod and Service annotations
- Controller logging level configuration
- Minio Customizations
- Changed the Secret configuration to properly represent the path of a secret instead of the actual contents
- Changed the names of the secret and service that are represented to mirror that of the underlying chart
* Adding in role bindings for minio secrets if installed
helm has issues with conditional sub charts of a sub chart so I think it'd be better to have minio not be installed as part of the chart by default so if you want to leverage this chart as part of another chart you don't have to worry about unintended resources getting created on cluster.
* moved workflow CRD into helpers.tpl
* added new values to values.yaml
* added UI cluster role and binding
* add workflow controller cluster role and binding
* added ui service account creator
* added workflow controller service account yaml
* reformatted values.yaml to group similar items
* tweaked files to reflect values.yaml changes
* setup minio stuff to match subchart model
* changes to reflect minio rework
* added README to explain chart a bit
* changes made to reflect minio values changes
* changes to reflect minio values changes (again)
* updating minio to latest version
* move the crd definition into it's own tpl file
* Parameterize artifact configuration
**What**
- Add parameterization of artifact store configuration
**Why**
Enables configuration of artifact repo secrets or omitting for use with IAM credentials
* Add workflow CRD definition to argo chart
**Why**
The workflow CRD must exist in order for argo to function
* artifactRepository values follow tree structure
* Deploy CRD as a pre-install hook
**What**
Using `lachlanevenson/k8s-kubectl`, which appears to be the most popular, off the shelf container with `kubectl` applied, run a job to apply the `workflow` crd.
**Why**
CRD is not, and cannot, be parameterized with release and so attempting to deploy as a regular template causes failures when installing subsequent releases.
