TEMP experiment B: a misspelled requirepass in the fixture

ci/valkey/fixtures.yaml

@@ -22,4 +22,8 @@ stringData:
   # password rather than an empty string on purpose: an empty one would produce
   # exactly the open server the chart refuses to start, and the run would fail
   # for the right reason at the wrong place.
-  auth-conf: requirepass ci-valkey-throwaway-password
+  # TEMPORARY, REVERTED IN THIS PR: "requirepas" instead of "requirepass", the
+  # typo that would otherwise start an open server that looks healthy. Expected:
+  # the init container refuses, the pod never runs the server, and its log names
+  # the field without printing it.
+  auth-conf: requirepas ci-valkey-throwaway-password

ci/valkey/test-values.yaml

@@ -18,17 +18,6 @@ persistence:
   size: 128Mi
 
 valkey:
-  # TEMPORARY, REVERTED IN THIS PR: readiness authenticates with a deliberately
-  # wrong password while the server keeps the right one, to prove in the cluster
-  # that this probe CAN fail. Expected: startup passes, readiness fails with
-  # "NOAUTH Authentication required.", the pod stays 0/1 and the rollout wait
-  # times out.
-  readinessProbe:
-    exec:
-      command:
-        - /bin/sh
-        - -ec
-        - VALKEYCLI_AUTH=deliberately-wrong-password valkey-cli -e -p 6379 ping | grep -qx PONG
   # Small, so the whole thing stays inside the runner's budget. It still
   # exercises the derivation: 64Mi x limitFactor 3 = 192Mi limit, maxmemory =
   # 0.75 x that = 144Mi - and the render aborts if a configured maxmemory ever