OptionaladminOptional admin password secret name as defined in AWS Secrets Manager (plaintext). This allows to control admin password across the enterprise. Password will be retrieved and stored as a non-reversible bcrypt hash. Note: at present, change of password may require manual restart of argocd server.
OptionalbootstrapIf provided, the addon will bootstrap the app or apps in the provided repository.
In general, the repo is expected to have the app of apps, which can enable to bootstrap all workloads,
after the infrastructure and team provisioning is complete.
When GitOps mode is enabled via ArgoGitOpsFactory for deploying the AddOns, this bootstrap
repository will be used for provisioning all HelmAddOn based AddOns.
OptionalbootstrapOptional values for the bootstrap application. These may contain values such as domain named provisioned by other add-ons, certificate, and other parameters to pass to the applications.
OptionalchartChart name
OptionaldependencyIndicate the helm chart provided uses dependency mode (https://helm.sh/docs/helm/helm_dependency/).
Dependency mode is widely used in aws-samples/eks-blueprints-add-ons repository, for example:
https://github.com/aws-samples/eks-blueprints-add-ons/blob/main/add-ons/appmesh-controller/Chart.yaml
Dependency mode requires the chart values to be wrapped within the chart name.
This value is only used to turn off dependency mode in case customers choose to copy the whole helm chart into their repo
OptionalnameName of the helm chart (add-on)
OptionalnamespaceNamespace where add-on will be deployed.
OptionalreleaseHelm release
OptionalrepositoryHelm repository
OptionalskipWhen global helm version validation is enabled with HelmAddOn.validateHelmVersions = true allows to skip validation for a particular helm add-on.
OptionalvaluesValues to pass to the chart as per https://github.com/argoproj/argo-helm/blob/master/charts/argo-cd/values.yaml.
OptionalversionHelm chart version to use to install.
OptionalworkloadAdditional GitOps applications and repositories. If there is a split between infra and application repositories then bootstrap repo is expected to be leveraged for infrastructure and application deployments will contain additional applications.
Configuration options for add-on.