From 1f46db8609b4f8e8dabebb72b1b40916eee0a8b7 Mon Sep 17 00:00:00 2001 From: Stefan Prodan Date: Fri, 11 Feb 2022 17:11:18 +0200 Subject: [PATCH] Fix Flux mention in API docs Signed-off-by: Stefan Prodan --- docs/spec/v2beta1/helmreleases.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/spec/v2beta1/helmreleases.md b/docs/spec/v2beta1/helmreleases.md index e069cb1..41438db 100644 --- a/docs/spec/v2beta1/helmreleases.md +++ b/docs/spec/v2beta1/helmreleases.md @@ -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.