if admin secret is created stop creating csi secret from the rook operator the csi creds and secret will still be created by the python and the import script Signed-off-by: parth-gr <partharora1010@gmail.com>
21 lines
1.0 KiB
Markdown
21 lines
1.0 KiB
Markdown
# v1.19 Pending Release Notes
|
|
|
|
## Breaking Changes
|
|
|
|
- The behavior of the `activeStandby` property in the `CephFilesystem` CRD has changed.
|
|
When set to `false`, the standby MDS daemon deployment will be scaled down and removed,
|
|
rather than only disabling the standby cache while the daemon remains running.
|
|
|
|
- Now rook operator won't create the csi user and secrets for external mode when admin keyring is used.
|
|
There will be a single source of truth. The python script will be responsible for creating the ceph user
|
|
and the import script will handle creating the kubernetes secrets for ceph user. [PR](https://github.com/rook/rook/pull/16882)
|
|
|
|
## Features
|
|
|
|
- Experimental: Allow concurrent reconciles of the CephCluster CR when there multiple clusters
|
|
being managed by the same Rook operator. Concurrency is enabled by increasing
|
|
the operator setting `ROOK_RECONCILE_CONCURRENT_CLUSTERS` to a value greater
|
|
than `1`.
|
|
- Improved logging with namespaced names for the controllers for more consistency in
|
|
troubleshooting the rook operator log.
|