Michael Adam

@travisn , @subhamkrai - what do you think? - is this something that should be documented?

I can confirm @BlaineEXE's suggestion from the huddle: directly invoking `bin/kubectl-rook-ceph` works. no need to `kubectl krew install` it

@subhamkrai , in my local build, the build already has a completion command: ``` $ ./bin/kubectl-rook-ceph kubectl rook-ceph provides common management and troubleshooting tools for Ceph. Usage: rook-ceph [command] Available...

@subhamkrai I tried it locally and I can confirm that it currently works for neither the locally bilt `kubectl-rook-ceph` binary nor for the installed plugin `kubectl rook-ceph` I am not...

@anoopcs9 wrote: > > They also offer the required Samba packages out of the box so there would not be a requirement to additionally create and maintain debian package builds...

@phlogistonjohn might a multi-stage build containerfile help with this?

do we still want this, or rather close it, @phlogistonjohn , @anoopcs9 ?

@ibotty wrote: > Any news? As @anoopcs9 has mentioned in the previous comment, I think this has long been done: * ad-server: #142 * server: #98 closing this issue as...

I am not certain which metrics ctdb could expose that would be meaningful to the casual bystander/observer. Everything I am aware of that ctdb can report would only be meaningful...