[artemiscloud-operator] - add support to skip artemiscloud-operator-c…

…rd dependency install

Signed-off-by: Tiago Bueno <[email protected]>

charts/artemiscloud-operator/Chart.yaml

@@ -35,4 +35,5 @@ dependencies:
 # This is needed because it must be a match of the operator CRD
     version: "0.2.1" 
     repository: https://tlbueno.github.io/helm-charts
+    condition: install_crds
 

charts/artemiscloud-operator/README.md

@@ -4,6 +4,7 @@ An helm chart to deploy the ArtemisCloud Operator
 
 The chart will:
 - create a namespace
+- deploy artemiscloud operator CRDs (optional)
 - deploy the artemiscloud operator
 
 ### How to use
@@ -22,10 +23,23 @@ helm install my-artemiscloud-operator -f ./my-values.yaml tlbueno/artemiscloud-o
 
 Default values:
 ```yaml
-# Default values for olm-operator-installer.
+# Default values for artemiscloud-operator.
 # This is a YAML-formatted file.
 # Declare variables to be passed into your templates.
 
+# If true it will deploy the dependency chart artemiscloud-operator-crds
+# If false it will skip the dependency install. In this case the CRD must be already installed
+# Setting this as false and installing the artemiscloud-operator-crds before
+# will let you manage the CRD versions in a different helm release, so, in this case
+# you can have different versions of the operator at the same time.
+# as an example, you can install artemiscloud-operator-crds for operator 1.2.1,
+# then install the artemiscloud-operator for operator 1.2.1,
+# then install the artemiscloud-operator for operator 1.1.0 in a different namespace
+# as the CRDs have backward compatibility and you installed the latest one,
+# you can have multiple operator versions at the same time but you need to ensure they are
+# watching specific namespaces otherwise it can have unexpected behavior
+install_crds: true
+
 namespace:
   # namespace where the operator will be installed
   name: artemiscloud-operator

charts/artemiscloud-operator/values.yaml

@@ -1,7 +1,20 @@
-# Default values for olm-operator-installer.
+# Default values for artemiscloud-operator.
 # This is a YAML-formatted file.
 # Declare variables to be passed into your templates.
 
+# If true it will deploy the dependency chart artemiscloud-operator-crds
+# If false it will skip the dependency install. In this case the CRD must be already installed
+# Setting this as false and installing the artemiscloud-operator-crds before
+# will let you manage the CRD versions in a different helm release, so, in this case
+# you can have different versions of the operator at the same time.
+# as an example, you can install artemiscloud-operator-crds for operator 1.2.1,
+# then install the artemiscloud-operator for operator 1.2.1,
+# then install the artemiscloud-operator for operator 1.1.0 in a different namespace
+# as the CRDs have backward compatibility and you installed the latest one,
+# you can have multiple operator versions at the same time but you need to ensure they are
+# watching specific namespaces otherwise it can have unexpected behavior
+install_crds: true
+
 namespace:
   # namespace where the operator will be installed
   name: artemiscloud-operator