Hit send too early...
So I did find in the code that it's looking for the deletion timestamp, but
deleting this field in the CRD does not stop the deletion request either.
The deletionTimestamp reappears after committing the change.
https://github.com/rook/rook/blob/23108cc94afdebc8f4ab144130a270b1e4ffd94e/…
On Thu, Sep 24, 2020 at 10:40 PM Peter Sarossy <peter.sarossy(a)gmail.com>
wrote:
hey folks,
I have managed to fat finger a config apply command and accidentally
deleted the CRD for one of my pools. The operator went ahead and tried to
purge it, but fortunately since it's used by CephFS it was unable to.
Redeploying the exact same CRD does not make the operator stop trying to
delete it though.
Any hints on how to make the operator forget about the deletion request
and leave it be?
--
Cheers,
Peter Sarossy
Technical Program Manager
Data Center Data Security - Google LLC.
--
Cheers,
Peter Sarossy
Technical Program Manager
Data Center Data Security - Google LLC.