[DOC-1057][2025.2] Configure ClockBound for YBA

docs/content/stable/yugabyte-platform/configure-yugabyte-platform/aws.md

@@ -175,6 +175,14 @@ Use this option with caution. Time synchronization is critical to database data
 
     {{< /warning >}}
 
+#### Configure ClockBound (optional)
+
+{{<tags/feature/ea idea="2133">}}[ClockBound](https://github.com/aws/clock-bound) improves clock accuracy by several orders of magnitude and significantly reduces read-restart errors in YSQL. To enable ClockBound for universes created using your provider, after you have created the provider, set the provider runtime configuration flag `yb.provider.configure_clockbound_cloud_provisioning` for the provider to `true`. Refer to [Manage runtime configuration settings](../../administer-yugabyte-platform/manage-runtime-config/).
+
+When enabled, ClockBound is automatically configured during node provisioning, and the universe creation task sets the [time_source](../../../reference/configuration/yb-master/#time-source) flag to `clockbound`.
+
+ClockBound is supported on AWS and GCP. (Azure and Kubernetes deployments are not supported.)
+
 ### Add regions
 
 For deployment, YBA aims to provide you with access to the many regions that AWS makes available globally. To that end, YBA allows you to select which regions to which you wish to deploy.

docs/content/stable/yugabyte-platform/configure-yugabyte-platform/gcp.md

@@ -192,6 +192,14 @@ You can customize the Network Time Protocol server, as follows:
 Use this option with caution. Time synchronization is critical to database data consistency; failure to run NTP may cause data loss.
     {{< /warning >}}
 
+#### Configure ClockBound (optional)
+
+{{<tags/feature/ea idea="2133">}}[ClockBound](https://github.com/aws/clock-bound) improves clock accuracy by several orders of magnitude and significantly reduces read-restart errors in YSQL. To enable ClockBound for universes created using your provider, after you have created the provider, set the provider runtime configuration flag `yb.provider.configure_clockbound_cloud_provisioning` for the provider to `true`. Refer to [Manage runtime configuration settings](../../administer-yugabyte-platform/manage-runtime-config/).
+
+When enabled, ClockBound is automatically configured during node provisioning, and the universe creation task sets the [time_source](../../../reference/configuration/yb-master/#time-source) flag to `clockbound`.
+
+ClockBound is supported on AWS and GCP. (Azure and Kubernetes deployments are not supported.)
+
 ### GCP instance templates
 
 You can optionally add a GCP [instance template](https://cloud.google.com/compute/docs/instance-templates) as a region-level property when creating a GCP provider in YBA.

docs/content/stable/yugabyte-platform/create-deployments/create-universe-multi-zone.md

@@ -38,6 +38,14 @@ For information on modifying or scaling an existing universe, refer to [Modify u
 
 Before you start creating a universe, ensure that you have created a provider configuration as described in [Create provider configurations](../../configure-yugabyte-platform/).
 
+### Configure ClockBound (optional)
+
+{{<tags/feature/ea idea="2133">}}[ClockBound](https://github.com/aws/clock-bound) improves clock accuracy and reduces read-restart errors in YSQL. To enable ClockBound for [cloud provider](../../configure-yugabyte-platform/aws/) universes, set the provider's `yb.provider.configure_clockbound_cloud_provisioning` runtime configuration flag to `true` (before creating the universe). Refer to [Manage runtime configuration settings](../../administer-yugabyte-platform/manage-runtime-config/).
+
+When enabled, ClockBound is automatically configured during node provisioning, and the universe creation task sets the [time_source](../../../../reference/configuration/yb-master/#time-source) flag to `clockbound`.
+
+ClockBound is supported on AWS and GCP. Azure and Kubernetes deployments are not supported.
+
 ## Create a universe
 
 To create a universe:

docs/content/stable/yugabyte-platform/prepare/server-nodes-software/software-on-prem.md

@@ -109,6 +109,7 @@ The following table describes options that are changed for a typical installatio
 | `use_system_level_systemd` | Defaults to false (which uses user-level systemd for service management). |
 | `node_ip` | The fully-qualified domain name or IP address of the node you are provisioning. Must be accessible to other nodes. |
 | `tmp_directory` | The directory on the node to use for storing temporary files during provisioning. |
+| `is_configure_clockbound` | {{<tags/feature/ea idea="2133">}}Set to `true` to configure [ClockBound](https://github.com/aws/clock-bound) during provisioning. ClockBound improves clock accuracy and reduces read-restart errors in YSQL. ClockBound requires [chrony](https://chrony-project.org/) to be configured. <br/>When enabled, the provisioning script installs ClockBound as a systemd unit and configures it to communicate with chronyd. <br/>The script also configures the on-premises provider configuration (see the following options) so that universes created using the provider automatically have the [time_source](../../../../reference/configuration/yb-master/#time-source) flag set to `clockbound`. |
 
 Set the following options to have node agent create (or update) the [on-premises provider configuration](../../../configure-yugabyte-platform/on-premises-provider/) where you want to add the node. (YugabyteDB Anywhere must be installed and running.)