* Description of problem (please be detailed as possible and provide log
snippests):

Documentation should emphasize the importance of time synchronization for OCS, as Ceph heavily depends on that.
This is especially important for customers going to use OCS in a restricted/disconnected network environment.

This happened to my customer:

- successfully installed OCP 4.3 on VMWare UPI in a restricted network
- after some some time (hours, days) they have deployed OCS 4.2.2 on OCP, time drift has happened on their VMs
- we've noticed that OCS stays in "degraded" state with CEPH status reporting "HEALTH_WARN, clock skew detected on mon.x"
- we've found Red Hat solution [ A newly deployed OCS 4 cluster status shows as "Degraded", Why? ] [1]
- with the information in [2], they were able to configure time-synchronization without full internet connectivity
- OCS 4.2.2 started to work

[1] https://access.redhat.com/solutions/4828941
[2] https://docs.openshift.com/container-platform/4.3/installing/install_config/installing-customizing.html#installation-special-config-crony_installing-customizing


* Is there any workaround available to the best of your knowledge?

Yes, KCS https://access.redhat.com/solutions/4828941
There are already many support cases linked to this one, so it will be very useful for our customers to have a better documentation here.

* Proposed documentation enhancement:

- Point to the importance of time synchronization in part [4] and/or [5] in the OCS 4.2 documentation
- Outline the need for configuring chrony to use an internal time source [2] when installing in a restricted network environment

[4] https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.2/html-single/planning_your_deployment/index
[5] https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/4.2/html-single/deploying_openshift_container_storage/index