1. Proposed title of this feature request
Control Over Defining timeout Value at time of installation.

// waitForStableOperators ensures that each cluster operator is "stable", i.e. the
// operator has not been in a progressing state for at least a certain duration,
// 30 seconds by default. Returns an error if any operator does meet this threshold
// after a deadline, 30 minutes by default. 

2. What is the nature and description of the request?
The request is to have no timeout hardcoded, allowing for provisioning even in cases of slow network connectivity.

3. Why does the customer need this? (List the business requirements here)
Without this, it will not be possible to build an OpenShift cluster, which would require deploying another flavor of Kubernetes. It appears that it is good practice in development not to hardcode parameters.
 
4. List any affected packages or components.
NA

5. Do you have a specific timeline, dependencies, and a preferred release for this feature request?
As soon as possible.

6. How would you like to achieve this? (Please list any functional requirements.)
Parameters should be adjustable to allow for flexibility in configuration.

7. What is the urgency of this feature request, and what is the business impact?
Customer response : It could decrease the speed of adoption of openshift in my company, if it is not implemented quickly.