NMO v0.7.0 (to be released with CNV 2.5) already uses operator-sdk 0.18.2 [0] and switched to leader-with-lease [1], so we are fine here.

[0] https://github.com/kubevirt/node-maintenance-operator/blob/release-0.7/go.mod#L10
[1] https://github.com/kubevirt/node-maintenance-operator/pull/117

Gary: When the NMO starts, at the start it will report the operator SDK version.

{"level":"info","ts":1601301253.1651402,"logger":"cmd","msg":"Version of operator-sdk: v0.18.2"}

Cluster Version: 4.6.0-0.nightly-2020-09-24-162403

Operator Version: kubevirt-hyperconverged-operator.v2.5.0

Node Maintenance Operator Logs: 
{"level":"info","ts":1601301253.1650724,"logger":"cmd","msg":"Go Version: go1.13.4"}
{"level":"info","ts":1601301253.165135,"logger":"cmd","msg":"Go OS/Arch: linux/amd64"}
{"level":"info","ts":1601301253.1651402,"logger":"cmd","msg":"Version of operator-sdk: v0.18.2"}
{"level":"info","ts":1601301253.165144,"logger":"cmd","msg":"Operator Version: 0.7.0-2-g8265363"}

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4196