Description of problem:
In Section 17.4.1. Disabling I/O Encryption for all the Volumes, step 4 specifies deleting the three gluster files glusterfs.pem, glusterfs.ca, glusterfs.key. For a setup where management encryption is also enabled, deleting these three files will result in glusterd failing on all the gluster pods.
A warning or note should be added to this step specifying the same.
Version-Release number of selected component (if applicable):
How reproducible: 1/1
Steps to Reproduce:
1. Enable I/O encryption and management encryption
2. Stop all volumes
3. Reset the auth.ssl-allow, client.ssl and server.ssl options
4. Remove glusterfs.pem, glusterfs.ca, glusterfs.key from all nodes
5. Stop glusterfs storage pods by deleting the daemonset
6. Create a new daemonset
Gluster pods fail to come up because glusterd service fails to start