diff --git a/ci/keycloak/test-values.yaml b/ci/keycloak/test-values.yaml
index 028808a..d3d7af1 100644
--- a/ci/keycloak/test-values.yaml
+++ b/ci/keycloak/test-values.yaml
@@ -181,20 +181,25 @@ keycloak:
   # the subpath hides nothing is a property of the mount path rather than a
   # measurement - and the kcLogoIdP line needs a browser plus a realm setting,
   # neither of which exists in CI.
-  extraVolumes:
-    - name: login-theme
-      configMap:
-        name: ci-keycloak-theme
-        items:
-          - key: theme.properties
-            path: login/theme.properties
-  extraVolumeMounts:
-    - name: login-theme
-      # THE SUBPATH, AND THE WHOLE POINT OF THE EXAMPLE: a volume on
-      # /opt/keycloak/themes would hide the image's own three themes and break
-      # the login page while the pod stayed Ready.
-      mountPath: /opt/keycloak/themes/ci-theme
-      readOnly: true
+  # TEMPORARILY DISABLED FOR AN A/B MEASUREMENT, RESTORED BEFORE THIS PR IS
+  # MERGED. Three of five runs with the mount restarted one pod once, while the
+  # three runs of PR #87 without it restarted none - too close to be dismissed
+  # and not establishable from a green log. So the control case is measured on
+  # the SAME runner: this commit is the chart's pre-#88 fixture, the next one
+  # puts the mount back with the numbers written down. If this commit is what
+  # reaches main, the restore was lost and the install-test no longer walks the
+  # path #88 added.
+  # extraVolumes:
+  #   - name: login-theme
+  #     configMap:
+  #       name: ci-keycloak-theme
+  #       items:
+  #         - key: theme.properties
+  #           path: login/theme.properties
+  # extraVolumeMounts:
+  #   - name: login-theme
+  #     mountPath: /opt/keycloak/themes/ci-theme
+  #     readOnly: true
 
 ingress:
   # Left ON although no ingress controller answers in CI: the point is that