fluxcd
/
helm-controller
mirror of https://github.com/fluxcd/helm-controller.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix Flux mention in API docs 

Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
This commit is contained in:
Stefan Prodan 2022-02-11 17:11:18 +02:00
parent 770f4e8d29
commit 1f46db8609
No known key found for this signature in database
GPG Key ID: 3299AEB0E4085BAF
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/spec/v2beta1/helmreleases.md
View File

@ -1222,10 +1222,11 @@ Chart as suggested by the
[offical Helm documentation](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/#method-2-separate-charts).
However, if you have to integrate and use many existing (upstream) Helm Charts, not being able to
upgrade the CRDs via FluxCD `HelmRelease` objects might become a cumbersome limitation within your GitOps
workflow. Therefore, FluxCD allows you to opt-in to upgrading CRDs by setting the `crds` policy on
upgrade the CRDs via Flux's `HelmRelease` objects might become a cumbersome limitation within your GitOps
workflow. Therefore, Flux allows you to opt-in to upgrading CRDs by setting the `crds` policy on
the `HelmRelease.spec.install` and `HelmRelease.spec.upgrade` objects.
The following UpgradeCRDs policies are supported:
The following CRD upgrade policies are supported:
- `Skip` Skip CRDs do neither install nor replace (update) any CRDs.
- `Create` Only create new CRDs which do not yet exist, neither update nor delete any existing CRDs.