If you use one of the multus-y features that enables the DHCP daemon, you'll get prometheus alerts about using deprecated APIs
The fixed PR https://github.com/openshift/cluster-network-operator/pull/598 still not in the latest nightly build openshift-release.svc.ci.openshift.org/releasestream/4.3.0-0.nightly/release/4.3.0-0.nightly-2020-04-23-225015 yet.
For some reason 4.3.18 was built with an out-of-date CNO? (It was built on 4/28 but has a version of CNO from early morning on 4/19). The 4.3 nightlies have the fix so it should be in 4.3.19...
OK, it appears that the apiserver in 4.3 stores DaemonSets as "extensions/v1beta1" regardless of how they're created: danw@p50:~> oc get ds --all-namespaces -o yaml|grep ^..apiVersion - apiVersion: extensions/v1beta1 - apiVersion: extensions/v1beta1 - apiVersion: extensions/v1beta1 - apiVersion: extensions/v1beta1 - apiVersion: extensions/v1beta1 - apiVersion: extensions/v1beta1 - apiVersion: extensions/v1beta1 - apiVersion: extensions/v1beta1 - apiVersion: extensions/v1beta1 - apiVersion: extensions/v1beta1 - apiVersion: extensions/v1beta1 - apiVersion: extensions/v1beta1 - apiVersion: extensions/v1beta1 - apiVersion: extensions/v1beta1 However, it *does* have the fix: danw@p50:~> oc rsh -n openshift-network-operator network-operator-6c854f4855-f7k2t head -5 /bindata/network/multus/003-dhcp-daemon.yaml {{if .RenderDHCP}} apiVersion: apps/v1 kind: DaemonSet metadata: name: dhcp-daemon whatever. The alert no longer exists any more anyway so the fix wasn't even necessary.