fix(operator): missed changes related to changing min value for priority

Author: ayuskauskas

chart/templates/skyhook-crd.yaml

@@ -476,7 +476,7 @@ spec:
               priority:
                 description: Priority determines the order in which skyhooks are applied. Lower values are applied first.
                 type: integer
-                minimum: 0
+                minimum: 1
                 default: 200
               serial:
                 default: false

docs/ordering_of_skyhooks.md

@@ -1,6 +1,6 @@
 # Ordering of Skyhooks
 ## What
-With v0.8.0 Skyhooks now always get applied in a repeatable and specific order. This also means that all Skyhooks will now be sequential, though packages within a Skyhook can be parallel. Each custom resource now supports a `priority` field which is a non-zero positive integer. Skyhooks will be processed in order starting from 0, any Skyhooks with the same `priority` will be processed by sorting them by their `metadata.name` field.
+With v0.8.0 Skyhooks now always get applied in a repeatable and specific order. This also means that all Skyhooks will now be sequential, though packages within a Skyhook can be parallel. Each custom resource now supports a `priority` field which is a non-zero positive integer. Skyhooks will be processed in order starting from 1, any Skyhooks with the same `priority` will be processed by sorting them by their `metadata.name` field.
 
 **NOTE**: Any Skyhook which does NOT provide a `priority` field will be assigned a priority value of 200.
 

k8s-tests/chainsaw/skyhook/simple-skyhook/chainsaw-test.yaml

@@ -24,7 +24,6 @@ kind: Test
 metadata:
   name: simple-skyhook
 spec:
-  # skip: false ##  this test doesn't seem to be useful, just slows things down, leaving it for, should delete at some point if still skipped
   timeouts:
     assert: 240s
   steps: