Santosh Pillai
Santosh Pillai
@BlaineEXE @nasirudheen This got delayed as I was looking into some other tasks. I'll work on this in the coming weeks. Thanks for suggesting the vault agent approach for injecting...
@nikhiljha This is already covered in the cluster CRD documentation [here](https://rook.io/docs/rook/v1.9/CRDs/ceph-cluster-crd/?h=network+configuration+settings#network-configuration-settings) This doesn't look like something that should be added to the quick start documentation. Let me know if that...
Do you mean the example [CR] (https://github.com/rook/rook/blob/8b512a14bb5726c8b7368c796ea60add2529f0e7/deploy/examples/cluster.yaml#L108) It mentions about `dualStack` and comments it out already. IMO, the current documentation should suffice. But I'll check with the team and get...
@aesca1er What do you mean by `pod-creating resources`? Can you please elaborate this a bit more. Do you mean Operator is not adding securityOontext to the Pods that it is...
@aesca1er Also wanted to check if starting privileged pods is something that might be helpful in the mean time. See [here](https://github.com/rook/rook/blob/1ae867049b49079b76696e68ee9b8f30216528bd/deploy/examples/operator.yaml#L522)
@cupnes Is this issue only limited to encrypted devices? Is there any error with the `expand-bluefs` init container for encrypted devices?
@13567436138 Please provide - Rook and ceph version - `ceph status` output - `rook-ceph-operator` logs - Logs if the failure `mon` and `mgr` pods.
@travisn Started looking into this now. Correct me if my understanding is wrong. - User prepares OSDs using `ceph-volume lvm batch --prepare --db-devices ` - OSD on `deviceA` needs to...
> > Steps 1, 2, 3 requires manual intervention by the user. The rook operator needs to be down during step `2` and `3`. Once OSD is ready to be...