Description of problem:
DNS cluster operator is taking ~5 hours for the daemonsets to roll out on a 250 node cluster during the upgrade from 4.6.9 -> 4.7.0-fc.2 even when the max unavilable replicas is set to 10% instead of 1 after patching https://bugzilla.redhat.com/show_bug.cgi?id=1880148:

  updateStrategy:
    rollingUpdate:
      maxUnavailable: 10%
    type: RollingUpdate

The replicas seem to still rollout one at a time: https://snapshot.raintank.io/dashboard/snapshot/NOB8VPaH1UUNQIdl2gl5CwREdiPiWYwX.

Logs: http://dell-r510-01.perf.lab.eng.rdu2.redhat.com/large-scale/4.7-sdn-kube-1.20/bugs/dns-slow-rollout-upgrades/
 
Version-Release number of selected component (if applicable):
4.7.0-fc.2

How reproducible:
We just ran the upgrade once for this version.

Steps to Reproduce:
1. Install a large scale cluster using 4.6.9 bits.
2. Upgrade to 4.7.0-fc.2
3. Monitor the upgrade timing of the dns cluster operator

Actual results:
1 replica of DNS daemonset is rolled out at a time.

Expected results:
10% of the replicas are rolled out at a time.

Additional info: