@@ -29,8 +29,8 @@ The two-step dance exists because `kubectl wait` fails immediately when the obje
       metadata:
         name: postgres-test
       status:
-        (conditions[?type == 'Ready'])[0]:
-          status: "True"
+        (conditions[?type == 'Ready']):
+        - status: "True"
 ```
 
 What this buys us:
 
@@ -34,8 +34,8 @@ spec:
           metadata:
             name: bucket-test
           status:
-            (conditions[?type == 'Ready'])[0]:
-              status: "True"
+            (conditions[?type == 'Ready']):
+            - status: "True"
     # Replaces `until kubectl get ...` + `kubectl wait --for=jsonpath=...`
     # pairs: one assert handles both existence and the status field.
     - assert:
 
@@ -37,8 +37,8 @@ spec:
             name: postgres-test
           status:
             # JMESPath filter: condition order in the array does not matter
-            (conditions[?type == 'Ready'])[0]:
-              status: "True"
+            (conditions[?type == 'Ready']):
+            - status: "True"
 
   - name: wait-init-job-complete
     try:
@@ -50,8 +50,8 @@ spec:
           metadata:
             name: postgres-test-init-job
           status:
-            (conditions[?type == 'Complete'])[0]:
-              status: "True"
+            (conditions[?type == 'Complete']):
+            - status: "True"
 
   - name: verify-services-and-endpoints
     try: