Helm-release
Parameters
| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| interval | string | Yes | Interval at which to reconcile the Helm release. | |
| annotations | map | No | Annotations for the workload | |
| chart | object | No | Chart defines the template of the v1.HelmChart that should be created for this HelmRelease. [[EmptyIf: .chartRef != null]] [[RequiredIf: .chartRef == null]] | |
| chartRef | object | No | ChartRef holds a reference to a source controller resource containing the Helm chart artifact. [[EmptyIf: .chart != null]] [[RequiredIf: .chart == null]] | |
| dependsOn | array | No | DependsOn may contain a meta.NamespacedObjectReference slice with references to HelmRelease resources that must be ready before this HelmRelease can be reconciled. | |
| driftDetection | object | No | DriftDetection holds the configuration for detecting and handling differences between the manifest in the Helm storage and the resources currently existing in the cluster. | |
| install | object | No | Install holds the configuration for Helm install actions for this HelmRelease. | |
| kubeConfig | object | No | KubeConfig for reconciling the HelmRelease on a remote cluster. When used in combination with HelmReleaseSpec.ServiceAccountName, forces the controller to act on behalf of that Service Account at the target cluster. If the --default-service-account flag is set, its value will be used as a controller level fallback for when HelmReleaseSpec.ServiceAccountName is empty. | |
| labels | map | No | Labels for the workload | |
| maxHistory | integer | No | MaxHistory is the number of revisions saved by Helm for this HelmRelease. Use '0' for an unlimited number of revisions; defaults to '5'. | |
| persistentClient | boolean | No | PersistentClient tells the controller to use a persistent Kubernetes client for this release. When enabled, the client will be reused for the duration of the reconciliation, instead of being created and destroyed for each (step of a) Helm action. This can improve performance, but may cause issues with some Helm charts that for example do create Custom Resource Definitions during installation outside Helm's CRD lifecycle hooks, which are then not observed to be available by e.g. post-install hooks. If not set, it defaults to true. | |
| postRenderers | array | No | PostRenderers holds an array of Helm PostRenderers, which will be applied in order of their definition. | |
| releaseName | string | No | ReleaseName used for the Helm release. Defaults to a composition of '[TargetNamespace-]Name'. | |
| rollback | object | No | Rollback holds the configuration for Helm rollback actions for this HelmRelease. | |
| serviceAccountName | string | No | The name of the Kubernetes service account to impersonate when reconciling this HelmRelease. | |
| storageNamespace | string | No | StorageNamespace used for the Helm storage. Defaults to the namespace of the HelmRelease. | |
| suspend | boolean | No | Suspend tells the controller to suspend reconciliation for this HelmRelease, it does not apply to already started reconciliations. Defaults to false. | |
| targetNamespace | string | No | TargetNamespace to target when performing operations for the HelmRelease. Defaults to the namespace of the HelmRelease. | |
| test | object | No | Test holds the configuration for Helm test actions for this HelmRelease. | |
| timeout | string | No | Timeout is the time to wait for any individual Kubernetes operation (like Jobs for hooks) during the performance of a Helm action. Defaults to '5m0s'. | |
| uninstall | object | No | Uninstall holds the configuration for Helm uninstall actions for this HelmRelease. | |
| upgrade | object | No | Upgrade holds the configuration for Helm upgrade actions for this HelmRelease. | |
| values | object | No | Values holds the values for this Helm release. [[TextEditor: YAML]] | |
| valuesFrom | array | No | ValuesFrom holds references to resources containing Helm values for this HelmRelease, and information about how they should be merged. |
Template
The following tabs display the definition's Cue template and the rendered YAML. The rendered YAML is the output of the Cue template when the definition is applied to a cluster.