Travis Nielsen

@obnoxxx This PR anyway needs to be reworked when we are ready to enable the csi operator by default, let's not worry about that for now.

> > There seems to be an issue with the rebase, or else not sure why this commit shows up: > > [test: check for panic when creating client profile](https://github.com/rook/rook/pull/14766/commits/0d7b380ff01bff3143d4b64a25f9607499786706)...

@guimou Added this in #10381, perhaps he is interested? Sounds good to simplify. If you can put together a prototype that would be helpful to see how it will simplify...

For added context, design for the new csi operator is [in progress](https://github.com/ceph/ceph-csi-operator/pull/1), and we will need to add design for rook integration as well. A consideration is whether the new...

Here are some thoughts on how Rook would integrate with the CSI Operator as found in the current [design doc](https://github.com/ceph/ceph-csi-operator/blob/main/docs/design/operator.md), also with some questions and suggestions for the operator design...

@Madhu-1 Thanks for the discussion and feedback. Based on the discussion, I'll revise my designs as such. Changed lines have a `*`. Further discussions on CRD naming will move to...

While the feature is now disabled, reopening to continue working on the fix...

@iPraveenParihar @Madhu-1 This is working already in Rook v1.18 with CephCSI v3.15, right? When could we get the documentation created?

@BlaineEXE Great summary of the design considerations, thanks for the thorough list of issues to consider. This is feeling more and more like a needed change. Just a few thoughts......

I have a prototype of a piece of this working, see more details [here](https://github.com/rook/rook/issues/15014#issuecomment-2573738843). It's essentially for creating a per-cluster rook operator. The main part missing from this full proposal...