The GRPC metrics exposed by both the provisioner pod and the node plugin pod on some port. Provisioner pod is running on the pod network and the daemonset pods run on the host network. sometimes starting the GRPC metrics by default can lead to node plugin pods crashloopback state this is due to the port conflict. Moreover, the GRPC metrics are not for the user it's for the one which will help to debug the time taken by cephcsi to serve each GRPC call. Enabling it by default won't be a good idea. So the plan is to disable it by default, If someone faces any issue it can be enabled later at some point in time. closes #7378 Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
929 B
929 B
Major Themes
v1.6...
K8s Version Support
Upgrade Guides
Breaking Changes
Ceph
- Support for adding OSDs via Drive Groups was removed. Please refer to the Ceph upgrade guide for migration instructions. See https://github.com/rook/rook/issues/7275 for more information.
Features
Core
Ceph
- Ceph Pacific support
- Multiple Ceph Filesystems (with Pacific only)
- CephClient CRD has been converted to use the controller-runtime library
- Extending the support of vault KMS configuration for Ceph RGW
- Enable disruption budgets (PDBs) by default for Mon, RGW, MDS, and OSD daemons
- Add CephFilesystemMirror CRD to deploy cephfs-mirror daemon
- Ceph OSD: as of Nautilus 14.2.14 and Octopus 15.2.9 if the OSD scenario is simple (one OSD per disk) we won't use LVM to prepare the disk anymore
- Disable CSI GRPC metrics by default