You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/vendor/testing-how-to.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -193,6 +193,7 @@ The `cluster prepare` command requires either a Helm chart archive or a director
193
193
```
194
194
195
195
For command usage, including additional options, see [cluster prepare](/reference/replicated-cli-cluster-prepare).
196
+
196
197
### Access Clusters
197
198
198
199
Compatibility Matrix provides the kubeconfig forclusters so that you can access clusters with the kubectl command line tool. For more information, see [Command line tool (kubectl)](https://kubernetes.io/docs/reference/kubectl/)in the Kubernetes documentation.
@@ -206,12 +207,12 @@ To access a cluster from the command line:
206
207
```
207
208
In the output of the command, verify that the `STATUS`for the target cluster is `running`. For command usage, see [cluster ls](/reference/replicated-cli-cluster-ls).
208
209
209
-
1. Run the following command to open a new shell session with the kubeconfig configured for the specified cluster:
210
+
1. Run the following command to open a new shell session with the kubeconfig configured for the cluster:
210
211
211
212
```bash
212
213
replicated cluster shell CLUSTER_ID
213
214
```
214
-
Where CLUSTER_ID is the unique ID for the cluster.
215
+
Where CLUSTER_ID is the unique ID for the running cluster that you want to access.
215
216
216
217
For command usage, see [cluster shell](/reference/replicated-cli-cluster-shell).
0 commit comments