Early Access track (#23160)

docs/content/preview/faq/yugabytedb-managed-faq.md

@@ -106,7 +106,7 @@ A YugabyteDB Aeon account is limited to a single Sandbox cluster; you can add as
 | [Connections](../../yugabyte-cloud/cloud-basics/create-clusters-overview/#sizing) | Up to 15 simultaneous connections | 15 per vCPU per node |
 | [Scaling](../../yugabyte-cloud/cloud-clusters/configure-clusters/) | None | Horizontal and Vertical |
 | [Backups](../../yugabyte-cloud/cloud-clusters/backup-clusters/) | None | Scheduled and on-demand |
-| [YugabyteDB version](#what-version-of-yugabytedb-does-my-cluster-run-on) | Innovation<br>Preview | Production<br>Innovation |
+| [YugabyteDB version](#what-version-of-yugabytedb-does-my-cluster-run-on) | Innovation<br>Preview<br>Early Access | Production<br>Innovation<br>Early Access |
 | Price | Free | [Pay-as-you-go and subscription](#how-is-yugabytedb-aeon-priced)<br>[Free trial available](../../yugabyte-cloud/managed-freetrial/) |
 | Support | Slack Community | Enterprise Support |
 
@@ -132,7 +132,7 @@ During a [maintenance window](../../yugabyte-cloud/cloud-clusters/cloud-maintena
 
 #### Cluster (YugabyteDB) version upgrade
 
-To keep up with the latest bug fixes, improvements, and security fixes, Yugabyte upgrades your cluster database to the [latest version](#what-version-of-yugabytedb-does-my-cluster-run-on). The database is upgraded to the latest release in the [release track](#what-version-of-yugabytedb-does-my-cluster-run-on) that was selected when the cluster was created (Innovation or Production for dedicated clusters, or Innovation or Preview for Sandbox clusters). Sandbox clusters are always in the preview track.
+To keep up with the latest bug fixes, improvements, and security fixes, Yugabyte upgrades your cluster database to the [latest version](#what-version-of-yugabytedb-does-my-cluster-run-on). The database is upgraded to the latest release in the [release track](#what-version-of-yugabytedb-does-my-cluster-run-on) that was selected when the cluster was created.
 
 Yugabyte only upgrades clusters during scheduled maintenance windows. Yugabyte notifies you in advance of any upcoming upgrade via email.
 
@@ -146,12 +146,13 @@ For more information, refer to [Maintenance windows](../../yugabyte-cloud/cloud-
 
 Dedicated clusters are provisioned with a **stable** release, from a YugabyteDB [stable release](/preview/releases/versioning/#release-versioning-convention-for-stable-releases) series. When creating a dedicated cluster, you can choose one of the following tracks:
 
-- Innovation, which has more frequent updates for faster access to new features.
-- Production, which has a slower update cadence and features only select stable release builds.
+- Production - Has less frequent updates, using select stable builds that have been tested longer in YugabyteDB Aeon.
+- Innovation - Updated more frequently, providing quicker access to new features.
+- Early Access - Updated more frequently, providing access to the most recent stable YugabyteDB release.
 
-In addition to the Innovation track, Sandbox clusters can be provisioned with a **preview** release, from the YugabyteDB [preview release](/preview/releases/versioning/#release-versioning-convention-for-preview-releases) series.
+In addition to the Innovation and Early Access tracks, Sandbox clusters can be provisioned with a **preview** release, from the YugabyteDB [preview release](/preview/releases/versioning/#release-versioning-convention-for-preview-releases) series.
 
-Once a cluster is created, it is upgraded with releases from the track that was assigned at creation (that is, either Innovation or Production for dedicated clusters, or Innovation or Preview for Sandbox clusters).
+Once a cluster is created, it is upgraded with releases from the track that was assigned at creation.
 
 To view the database version running on a particular cluster, navigate to the **Clusters** page; the database version is displayed next to the cluster name; hover over the version to see the release track.
 

docs/content/preview/yugabyte-cloud/cloud-basics/create-clusters-overview.md

@@ -167,8 +167,9 @@ Refer to [Scaling clusters](../../cloud-clusters/configure-clusters/).
 
 By default, clusters are created using a stable release, taken from the [stable release series](../../../releases/versioning/#release-versioning-convention-for-stable-releases) of YugabyteDB. You can choose to deploy your dedicated cluster using the following tracks:
 
-- Innovation - Updated more frequently, providing quicker access to new features.
 - Production - Has less frequent updates, using select stable builds that have been tested longer in YugabyteDB Aeon.
+- Innovation - Updated more frequently, providing quicker access to new features.
+- Early Access - Updated more frequently, providing access to the most recent stable YugabyteDB release.
 
 If you need a feature from the [preview release series](../../../releases/versioning/#release-versioning-convention-for-preview-releases) of YugabyteDB, contact {{% support-cloud %}} before you create your cluster. (Preview is also available for Sandbox clusters.)
 

docs/content/preview/yugabyte-cloud/cloud-basics/create-clusters/create-clusters-free.md

@@ -22,7 +22,7 @@ Your Sandbox cluster includes the following:
 
 - Single node.
 - Up to 2 vCPUs, 4 GB memory, and 10 GB of storage, depending on the cloud provider.
-- Access to [innovation and preview release tracks](../../../../faq/yugabytedb-managed-faq/#what-version-of-yugabytedb-does-my-cluster-run-on).
+- Access to [Preview, Innovation, and Early Access release tracks](../../../../faq/yugabytedb-managed-faq/#what-version-of-yugabytedb-does-my-cluster-run-on).
 - Available in all [regions](../../create-clusters-overview/#cloud-provider-regions).
 
 Share your feedback, questions, and suggestions with other users on the [YugabyteDB Community Slack]({{<slack-invite>}}).
@@ -42,7 +42,7 @@ To create a Sandbox cluster:
     - **Cluster Name**: Enter a name for the cluster.
     - **Provider**: Choose a cloud provider - AWS or GCP.
     - **Region**: Choose the region in which to deploy the cluster.
-    - **Database Version**: Choose Innovation or Preview track.
+    - **Database Version**: Choose the release track.
 
 1. Click **Add Current IP Address** to add your computer to the cluster [IP allow list](../../../cloud-secure-clusters/add-connections/). This allows you to connect to the cluster after it's created. You can also add existing allow lists in your account, or create a new allow list and add addresses manually. Click **Next** when you are done.
 

docs/content/preview/yugabyte-cloud/managed-automation/managed-cli/managed-cli-examples/managed-guide-api.md

@@ -45,7 +45,7 @@ To create your free [sandbox](../../../cloud-basics/create-clusters/create-clust
 
 ### Determine the database version
 
-YugabyteDB Aeon has [three release tracks](../../../../faq/yugabytedb-managed-faq/#what-version-of-yugabytedb-does-my-cluster-run-on), Innovation or Preview for Sandbox clusters, and Innovation or Production for dedicated clusters.
+YugabyteDB Aeon has [four release tracks](../../../../faq/yugabytedb-managed-faq/#what-version-of-yugabytedb-does-my-cluster-run-on), Early Access, Innovation, or Preview for Sandbox clusters, and Innovation, Production, or Early Access for dedicated clusters.
 
 To get the ID for the Preview track and add it to an environment variable, enter the following commands:
 

docs/content/preview/yugabyte-cloud/managed-automation/managed-cli/managed-cli-reference/managed-cli-cluster.md

@@ -72,7 +72,7 @@ Create a cluster.
 | --cluster-tier | Type of cluster. `Sandbox` or `Dedicated`. |
 | --cluster-type | Deployment type. `SYNCHRONOUS` or `GEO_PARTITIONED`. |
 | --credentials | Required. Database credentials for the default user, provided as key-value pairs.<br>Arguments:<ul><li>username</li><li>password</li></ul> |
-| &#8209;&#8209;database&#8209;version | Database version to use for the cluster. `Innovation`, `Production`, or `Preview`. |
+| &#8209;&#8209;database&#8209;version | Database version to use for the cluster. `Innovation`, `Production`, `Preview`, or `'Early Access'`. |
 | --default-region | The primary region in a [partition-by-region](../../../../cloud-basics/create-clusters/create-clusters-geopartition/) cluster. The primary region is where all the tables not created in a tablespace reside. |
 | --encryption-spec | CMK credentials for encryption at rest, provided as key-value pairs.<br>Arguments:<ul><li>cloud-provider - cloud provider (`AWS`, `AZURE`, or `GCP`); required</li></ul>Required for AWS only:<ul><li>aws-access-key - access key ID</li><li>aws-secret-key - secret access key</li><li>aws-arn - Amazon resource name of the CMK</li></ul>If not provided, you are prompted for the secret access key. AWS secret access key can also be configured using the YBM_AWS_SECRET_KEY [environment variable](../../managed-cli-overview/#environment-variables).<br><br>Required for GCP only:<ul><li>gcp-resource-id - cloud KMS resource ID</li><li>gcp-service-account-path - path to the service account credentials key file</li></ul>Required for Azure only:<ul><li>azu-client-id - client ID of registered application</li><li>azu-client-secret - client secret of registered application</li><li>azu-tenant-id - Azure tenant ID</li><li>azu-key-name - key name</li><li>azu-key-vault-uri - key vault URI in the form `https://myvault.vault.azure.net`</li></ul> |
 | --fault-tolerance | Fault domain for the cluster. `NONE`, `NODE`, `ZONE`, or `REGION`. |
@@ -164,7 +164,7 @@ Update the specified cluster.
 | --cloud-provider | Cloud provider. `AWS`, `AZURE`, or `GCP`. |
 | --cluster-tier | Type of cluster. `Sandbox` or `Dedicated`. |
 | --cluster-type | Deployment type. `SYNCHRONOUS` or `GEO_PARTITIONED`. |
-| &#8209;&#8209;database&#8209;version | Database version to use for the cluster. `Innovation`, `Production`, or `Preview`. |
+| &#8209;&#8209;database&#8209;version | Database version to use for the cluster. `Innovation`, `Production`, `Preview`, or `'Early Access'`. |
 | --fault-tolerance | Fault domain for the cluster. `NONE`, `NODE`, `ZONE`, or `REGION`. |
 | --new-name | The new name for the cluster. |
 | --node-config <br> [Deprecated in v0.1.19] | Number of vCPUs and disk size per node for the cluster, provided as key-value pairs.<br>Arguments:<ul><li>num-cores - number of vCPUs per node</li><li>disk-size-gb - disk size in GB per node</li><li>disk-iops - disk IOPS per node (AWS only)</li></ul>If specified, num-cores is required and disk-size-gb and disk-iops are optional. |

docs/content/preview/yugabyte-cloud/release-notes.md

@@ -19,6 +19,12 @@ On this page:
 
 ## Change log
 
+### July 10, 2024
+
+**Database**
+
+- Ability to choose the latest [stable release](../../faq/yugabytedb-managed-faq/#what-version-of-yugabytedb-does-my-cluster-run-on) when creating a dedicated or Sandbox cluster using the new Early Access track. Early Access has more frequent updates for faster access to the most recent stable version of YugabyteDB. Currently features YugabyteDB v2024.1.0.0.
+
 ### June 24, 2024
 
 **New Features**