Comment 1 for bug 1916620

I recalled past issues that relate to this problem, and I am listing them below for background reference:

Bug 1850438;
Bug 1885229;
Bug 1896631;

(One relevant comment in the last one above is: "There is a race between the kubernetes processes coming up after the controller manifest is applied and the application of the worker manifest. (...) The fix for this would be quite extensive, requiring the creation of a new AIO, or separate kubernetes manifest to coordinate the bring-up of k8s services and the worker configuration.")

Bug 1900736.

While the final solution of avoiding the race condition is not ready yet, the timeout value will be increased to consider different loading from pods. For better evaluation of that, some measurements will be taken considering:

- Different number and types of pods;
- Different values of timeout.