Does it support encryption of networks in existing clusters?

[pluser]

Could you tell me whether it is supported to change the fields under spec.network.connections after cluster creation?
I'd like to change connections.encryption.enable to true but found the following caution in the official doc.

rook/Documentation/CRDs/Cluster/ceph-cluster-crd.md

Lines 223 to 225 in bc78b6c

	!!! caution
	Changing networking configuration after a Ceph cluster has been deployed is NOT
	supported and will result in a non-functioning cluster.

However, this description has existed before connections field has introduced and the meaning of connections field is different from other fields in network field very much. Changing the fields under connections results in the execution of ceph config. This is a normal operation for admins.

FYI, I verified setting connections.encryption.enable: true did not cause any problems in my cluster.

[travisn]

As I recall, changing the network.connection.encryption.enabled setting may cause issues with existing mounted volumes. @Madhu-1 ?

[Madhu-1]

@pluser Thank you, for RBD to work as the Rook set the default for rbd map options for CephFS csi sets the kernel mount options, its good to test cephfs/RBD to ensure the support works as expected.

[pluser]

Thank you, for RBD to work as the Rook set the default for rbd map options for CephFS csi sets the kernel mount options, its good to test cephfs/RBD to ensure the support works as expected.

@Madhu-1 Should I test CephFS case to state the caution that I mentioned doesn't apply to encryption field?

[pluser]

@Madhu-1
So, Final conclusion is that encryption is supported for networks in existing clusters, correct?
If you mean that CephFS is exception, we can verify this.

[Madhu-1]

AFAIK yes it can be supported.