Feature-Request: Provide different different profiles to manage update and reaction behavior in different scenarios

1. Proposed title of this feature request
Feature-Request: Provide different different profiles to manage update and reaction behavior in different scenarios

2. What is the nature and description of the request?
In some environments, the default values of `kubernetes` to handle OpenShift - Node failures is not necessary suitable as the use-case may require faster update and reaction time or even slower update and reaction time (for example with remote workers).

Allowing to modify specific parameters may not lead to the desired outcome as adjusting these settings needs to be carefully reviewed and the change need to be reflected in multiple areas. Kubernetes Reliability contains some very good examples and details of what needs to be considered.

This is why it's recommended to create some profiles that can be applied and that will provide behavior similar to what is documented in Kubernetes Reliability. Potentially creating 3 profiles as documented in might be a good starting point (the values of course can be adjusted based on experience respectively after sanity checking).

3. Why does the customer need this? (List the business requirements here)
In case of OpenShift remote workers it may be required to allow slow update and slow reaction while in some specific environments it may be required to capture failures fast and also react fast.

Having the option to apply a given profile will allow customers to chose an option to address certain needs (if the default does not work) and still remain in the acceptable and supported boundaries.

4. List any affected packages or components.
kubelet and Kubernetes Controller Manager