Skip to content

Commit f29fd7f

Browse files
committed
change command name back
1 parent 97cf782 commit f29fd7f

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

docs/enterprise/embedded-manage-nodes.mdx

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Multi-node clusters with Embedded Cluster have the following limitations:
1818

1919
* Setting node roles with the Embedded Cluster Config [roles](/reference/embedded-config#roles) key is Beta.
2020

21-
* The `get join-command` command always returns the commands for joining a node with the controller role. It does not support printing the join command for any custom node roles defined in the Embedded Cluster Config `roles` key. See [Automate Controller Node Joins (Beta)](#automate-node-joins) below.
21+
* The `join print-command` command always returns the commands for joining a node with the controller role. It does not support printing the join command for any custom node roles defined in the Embedded Cluster Config `roles` key. See [Automate Controller Node Joins (Beta)](#automate-node-joins) below.
2222

2323
## Add Nodes to a Cluster (Beta) {#add-nodes}
2424

@@ -52,7 +52,7 @@ To add a node to a cluster with Embedded Cluster in online (internet-connected)
5252

5353
1. SSH onto the node that you want to join.
5454

55-
1. Copy the curl command provided in the Admin Console to download the Embedded Cluster binary and then run it on the node you want to join.
55+
1. Copy the curl command provided in the Admin Console to download the Embedded Cluster binary and then run it on the node you want to join. In air gap installations,
5656

5757
1. Copy and run the tar command to extract the Embedded Cluster binary.
5858

@@ -107,7 +107,7 @@ To automate controller node joins with Embedded Cluster:
107107
1. On a node that is already joined to the cluster, run the following command:
108108

109109
```bash
110-
sudo ./APP_SLUG get join-command
110+
sudo ./APP_SLUG join print-command
111111
```
112112
Where `APP_SLUG` is the unique application slug.
113113

@@ -116,7 +116,7 @@ To automate controller node joins with Embedded Cluster:
116116
**Example:**
117117

118118
```
119-
sudo ./your-app-slug get join-command
119+
sudo ./your-app-slug join print-command
120120
121121
curl -k https://172.17.0.2:30000/api/v1/embedded-cluster/binary -o embedded-cluster.tar.gz && \
122122
tar -xvf embedded-cluster.tar.gz && \
@@ -125,7 +125,7 @@ To automate controller node joins with Embedded Cluster:
125125
**Example with JSON output:**
126126

127127
```
128-
sudo ./your-app-slug get join-command -ojson
128+
sudo ./your-app-slug join print-command -ojson
129129
130130
{
131131
"commands": [
@@ -136,7 +136,7 @@ To automate controller node joins with Embedded Cluster:
136136
}
137137
```
138138

139-
1. On the node that you want to join as a controller, run each of the commands provided in the `get join-command` output to download the Embedded Cluster binary, extract the binary, and join the node to the cluster.
139+
1. On the node that you want to join as a controller, run each of the commands provided in the `join print-command` output to download the Embedded Cluster binary, extract the binary, and join the node to the cluster.
140140

141141
## High Availability for Multi-Node Clusters (Alpha) {#ha}
142142

@@ -185,7 +185,7 @@ To create a multi-node HA cluster:
185185
1. Get the commands for downloading the Embedded Cluster binary, extracting the binary, and joining the third controller node either in the Admin Console **Cluster Management** tab or by running the following command on an existing node:
186186

187187
```bash
188-
sudo ./APP_SLUG get join-command
188+
sudo ./APP_SLUG join print-command
189189
```
190190
Where `APP_SLUG` is the unique application slug.
191191

0 commit comments

Comments
 (0)