feedc0de/my-rook-config
1
0 Fork 0
forked from rook/rook
Code Pull Requests Activity

docs: note that changing encryption option settings for existing clusters is not dangerous

Browse Source 
We have prohibited changing all network-related configurations after cluster creation.
However, as a result of https://github.com/rook/rook/discussions/13584, we found that
the connections.encryption flag can be regarded as an exception.

Signed-off-by: ESASHIKA Kaoru <kaoru-esashika@cybozu.co.jp>
This commit is contained in:
ESASHIKA Kaoru committed 2024-03-07 09:30:43 +00:00
1 parent 66fba39eab
commit 9ceb8aa7e0
1 file changed
+3 -2
Download Patch File Download Diff File Expand all files Collapse all files
Documentation/CRDs/Cluster/ceph-cluster-crd.md
+3 -2
View File
@@ -220,8 +220,9 @@ Configure the network that will be enabled for the cluster and services.
See the kernel requirements above for encryption.
!!! caution
Changing networking configuration after a Ceph cluster has been deployed is NOT
supported and will result in a non-functioning cluster.
Changing networking configuration after a Ceph cluster has been deployed is only supported for
the network encryption settings. Changing other network settings is *NOT* supported and will
likely result in a non-functioning cluster.
#### Provider