docs: Update 4.3 Docs

[balaharish7]

No description provided.

[Abhinandan-Purkait]

@balaharish7 Did you miss pushing your changes? I can't see them for the comments you marked as resolved.

[balaharish7]

@balaharish7 Did you miss pushing your changes? I can't see them for the comments you marked as resolved.

Can you check now.

[dsharma-dc]

Migration Steps

1. Identify all the volumes to be converted to encrypted, and change their spec to encrypted via plugin.
   kubectl mayastor set volume <volume_uuid> encryption true
2. Identify Target Pool: Select a non-encrypted pool (Example: P1) to migrate.
3. Identify all volumes with replicas on P1.
4. (Optional) Scale Up Volumes: Increase replica count (Example: from 2 to 3) to maintain availability.
5. Mayastor Cordon Node: Cordon the mayastor node hosting P1 to stop new replicas from being scheduled using the plugin command kubectl mayastor cordon node N1 <cordon_label>.
6. Scale Down Volumes: Reduce replica count to remove replicas from P1. In effect, this is like draining the pool.
7. Recreating as Encrypted Pool:
   • Delete the non-encrypted pool.
   • Uncordon the node.
   • Recreate it with encryption using the previously defined secret.
8. Scale-up Volumes: Increase replica count to allow new encrypted replicas to be created on the new pool.
9. Optional Replica Adjustment: After migration, optionally reduce replica count back to the original.