dcaputo-harmoni

This would be a very useful feature; any production environment likely needs some form of authentication header. We are having to resort to curl statements for testing.

@tiagolobocastro Just want to chime in on this issue as we are doing some pre-launch testing of our new k8s infrastructure that is based on openebs and learned the hard...

@tiagolobocastro yes new nodes were created with new names, that's unfortunately just how Azure VMSS's work - they recreate the VM's / nodes on certain changes. So while the drives...

@tiagolobocastro you mentioned in another ticket that there is a possible way to recover a cluster in this scenario that "wasn't user friendly" - would you mind outlining those steps...

@tiagolobocastro that is really helpful context. Why not have it automatically update those values when the node name changes in the DiskPool CR, ie if you have an existing DiskPool,...

@tiagolobocastro @Abhinandan-Purkait Thanks for the feedback and comments. I'm surprised honestly that basic stuff such as this is not already built into such a widely used project as openebs. The...

@tiagolobocastro @Abhinandan-Purkait I'm trying to develop a manual solution to this issue which I'll make available to the community as soon as it is complete so that others in the...

One further thought on this - it could behave just like the `revoke: true` flag within the VaultDynamicSecret spec, however the trigger would also encompass deletion of the underlying kubernetes...

I am seeing this same error (`attach failed: IO error: Input/output error (os error 5)`) after taking one node down and bringing it back up. When running `kubectl-mayastor get volumes`...

@tiagolobocastro Unfortunately I had to kill and restore the cluster right after this happened, and didn't get a chance to export the data you are looking for before I did....