During the fix of flaky machineConfigRollout tests on aks it was noticed that the time taken for the configUpdating status on the nodepool to appear was longer than expected.

Times observed were in the range of 10-20 seconds, when were expecting this to be reflected within 5seconds.

    4.18

    100%

    1. Check the test logs for e2e and search `start config update` this will point you to the tests logs that include replace and inplace nodepoolConfigUpdate and should also report the time it took for the condition to be reported.
    2.
    3.
    

    We ideally would want this under 5 seconds or atleast to understand why the times here are longer when comapared to local runs of the test.

    updatingConfig condition reported in < 5 seconds