rook-ceph: revert changes due to hard crash despite kernel updates

system-apps/rook-ceph/clusters/cluster.yaml

@@ -33,12 +33,12 @@ spec:
         keyGeneration: 2 # must be greater than the current keyGeneration
       csi:
         keyRotationPolicy: KeyGeneration
-        keyGeneration: 4 # must be greater than the current keyGeneration
+        keyGeneration: 5 # must be greater than the current keyGeneration
-        keyType: aes256k
+        keyType: aes # Talos kernel 6.18 / cephcsi v3.17.0 don't support aes256k yet
       rbdMirrorPeer:
         keyRotationPolicy: KeyGeneration
-        keyGeneration: 4 # must be greater than the current keyGeneration
+        keyGeneration: 5 # must be greater than the current keyGeneration
-        keyType: aes256k
+        keyType: aes # Talos kernel 6.18 / cephcsi v3.17.0 don't support aes256k yet
   # The path on the host where configuration files will be persisted. Must be specified. If there are multiple clusters, the directory must be unique for each cluster.
   # Important: if you reinstall the cluster, make sure you delete this directory from each host or else the mons will fail to start on the new cluster.
   # In Minikube, the '/data' directory is configured to persist across reboots. Use "/data/rook" in Minikube environment.
@@ -370,4 +370,13 @@ spec:
       mgr:
         disabled: false
       osd:
-        disabled: false
+        disabled: false
+    muteHealthWarning: # Remove these after Talos uses 7.0+ kernel
+      AUTH_INSECURE_ROTATING_SERVICE_KEY_TYPE:
+        policy: mute
+      AUTH_INSECURE_CLIENT_KEY_TYPE:
+        policy: mute
+      AUTH_INSECURE_KEYS_ALLOWED:
+        policy: mute
+      AUTH_INSECURE_KEYS_CREATABLE:
+        policy: mute