Fix reinit issues

Fix leftover reinit daemonset, when multiple reinit happened at the same time

config/helm/generic-values.yaml

@@ -0,0 +1,5 @@
+# Values defined in this file are specific to running the compliance-operator
+# on a Generic Kubernetes Cluster. All other values use the defaults defined in values.yaml.
+platform: generic
+nodeSelector: 
+tolerations: null

config/helm/hypershift-values.yaml

@@ -0,0 +1,6 @@
+# Values defined in this file are specific to running the compliance-operator
+# on HyperShift Hosted Cluster. All other values use the defaults defined in values.yaml.
+platform: hypershift
+nodeSelector:
+  node-role.kubernetes.io/worker: ""
+tolerations: null

config/helm/values.yaml

@@ -8,7 +8,7 @@
 namespace: openshift-compliance
 
 # The default platform for the compliance-operator. Available platforms are
-# 'openshift', 'eks', 'generic', and 'unknown'.
+# 'openshift', 'eks', 'generic', 'hypershift' and 'unknown'.
 platform: openshift
 
 # By default, the compliance-operator will deploy to nodes tagged with the

doc/install.md

@@ -76,6 +76,18 @@ you can run the compliance-operator on EKS using the EKS-specific overrides in
 $ helm install . --namespace openshift-compliance --generate-name -f eks-values.yaml
 ```
 
+To install on Generic Kubernetes, use the `generic-values.yaml` file:
+
+```
+$ helm install . --namespace openshift-compliance --generate-name -f generic-values.yaml
+```
+
+To install on HyperShfit Hosted Cluster, use the `hypershift-values.yaml` file:
+
+```
+$ helm install . --namespace openshift-compliance --generate-name -f hypershift-values.yaml
+```
+
 You can use Helm to uninstall, or delete a release, but Helm does not cleanup
 [custom resource
 definitions](https://helm.sh/docs/chart_best_practices/custom_resource_definitions/#helm).