Fix docs for xcluster DDL flow for YCQL & onprem provider ssh user (#…

…23827)
yugabyte · Sep 8, 2024 · 3ba74e8 · 3ba74e8
1 parent 35add07
commit 3ba74e8
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/...t/preview/yugabyte-platform/configure-yugabyte-platform/on-premises-provider.md b/...t/preview/yugabyte-platform/configure-yugabyte-platform/on-premises-provider.md
@@ -68,7 +68,7 @@ For on-premises deployments, consider racks as zones to treat them as fault doma
 
 ### SSH Key Pairs
 
-In the **SSH User** field, enter the name of the user that has SSH privileges on your instances. This is required because YBA needs SSH access to the nodes to provision them with YugabyteDB. Unless you plan to provision the database nodes manually, the SSH user needs to have password-free sudo permissions to complete a few tasks.
+In the **SSH User** field, enter the name of the user that has SSH privileges on your instances. This is required because YBA needs SSH access to the nodes to provision them with YugabyteDB. This SSH user cannot be named yugabyte. Unless you plan to provision the database nodes manually, the SSH user needs to have password-free sudo permissions to complete a few tasks.
 
 If the SSH user requires a password for sudo access or the SSH user does not have sudo access, you must enable the **Manually Provision Nodes** option (under **Advanced**) and [manually provision the instances](../on-premises-script/).
 

diff --git a/...te-platform/manage-deployments/xcluster-replication/xcluster-replication-ddl.md b/...te-platform/manage-deployments/xcluster-replication/xcluster-replication-ddl.md
@@ -60,7 +60,7 @@ Perform DDL operations in the order as shown in the following table. The order v
 | :-- | :----- | :----- | :----- |
 | CREATE TABLE | Execute on Source | Execute on Target | [Add table to replication](#add-a-table-to-replication) |
 | DROP TABLE   | [Remove table from replication](#remove-a-table-from-replication) | Execute on Target | Execute on Source |
-| CREATE INDEX | Execute on Source | Execute&nbsp;on&nbsp;Target | [Reconcile&nbsp;configuration](#reconcile-configuration) |
+| CREATE INDEX | Execute on Source | Execute&nbsp;on&nbsp;Target | [Add table to replication](#add-a-table-to-replication)  |
 | DROP INDEX   | [Remove index table from replication](#remove-a-table-from-replication) | Execute on Target | Execute on Source |
 | ALTER TABLE or INDEX | Execute&nbsp;on&nbsp;Target | Execute&nbsp;on&nbsp;Source | No changes needed |
 

diff --git a/...nt/stable/yugabyte-platform/configure-yugabyte-platform/on-premises-provider.md b/...nt/stable/yugabyte-platform/configure-yugabyte-platform/on-premises-provider.md
@@ -68,7 +68,7 @@ For on-premises deployments, consider racks as zones to treat them as fault doma
 
 ### SSH Key Pairs
 
-In the **SSH User** field, enter the name of the user that has SSH privileges on your instances. This is required because YBA needs SSH access to the nodes to provision them with YugabyteDB. Unless you plan to provision the database nodes manually, the SSH user needs to have password-free sudo permissions to complete a few tasks.
+In the **SSH User** field, enter the name of the user that has SSH privileges on your instances. This is required because YBA needs SSH access to the nodes to provision them with YugabyteDB. This SSH user cannot be named yugabyte. Unless you plan to provision the database nodes manually, the SSH user needs to have password-free sudo permissions to complete a few tasks.
 
 If the SSH user requires a password for sudo access or the SSH user does not have sudo access, you must enable the **Manually Provision Nodes** option (under **Advanced**) and [manually provision the instances](../on-premises-script/).