Parth Arora
Probably they are asking similar to this https://github.com/rook/rook/pull/11336
@karthik-us just a suggestion for future you should self-assign the issue before opening a PR, something like this https://rook.io/docs/rook/latest-release/Contributing/development-flow/#self-assign-issue
@rkachach So in this case we need to run the Python file with user input flags, how can we design so user can directly use the binary at ceph standalone...
Refactor(python to python framework): 1) Have a separate file for rgw, file and block 2) have a proper build way 3) Testing should be done more deeply 4) Handel upgrade...
sure use this https://rook.io/docs/rook/latest-release/Contributing/development-flow/#self-assign-issue
@smoshiur1237 Yes having a separate directory for the external cluster works, with specific external files, and you need to update all the documentation where we link manifests in the doc....
Okay that fit perfectly
> Most commonly, users have either an internal or external cluster, but not both. While it's possible to have both, it would be good to create the examples for the...
@urbaman >The Tollbox, if running in the same namespace as the cluster, has RADOS permission errors. Can you open a separate issue, generally we wont require toolbox pod in external...