In order to be able to run MCO automation in prow while using a maUnavailable value different from 1, we need to:

• Adapt the test cases that test maxUnavailable, so that they restore the original maxUnavailable value instead of 1. Right now they set the maxValue that they want to test and then the set it back to 1 instead of setting it back to the original value.

• Create a step in prow that configures the maxUnavailable value in the pools. We need to take into account that master pool only support maxUnavailable=1