Skip to content

Commit cd59f5e

Browse files
committed
edits
1 parent 845ce80 commit cd59f5e

File tree

2 files changed

+10
-4
lines changed

2 files changed

+10
-4
lines changed

docs/reference/replicated-cli-cluster-shell.mdx

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,5 @@
1+
import Help from "../partials/replicated-cli/_help.mdx"
2+
13
# cluster shell
24

35
Opens a new shell session with the kubeconfig configured for the specified cluster. This allows you to have immediate kubectl access to the cluster within the shell environment.

docs/vendor/testing-how-to.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -206,19 +206,23 @@ To access a cluster from the command line:
206206
```
207207
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).
208208

209-
1. Run the following command to download the kubeconfig for the cluster and update Kubernetes context:
209+
1. Run the following command to open a new shell session with the kubeconfig configured for the specified cluster:
210210

211211
```bash
212-
replicated cluster kubeconfig CLUSTER_ID
213-
```
214-
When the command completes, a `Updated kubernetes context` message is displayed. For command usage, see [cluster kubeconfig](/reference/replicated-cli-cluster-kubeconfig).
212+
replicated cluster shell CLUSTER_ID
213+
```
214+
Where CLUSTER_ID is the unique ID for the cluster.
215+
216+
For command usage, see [cluster shell](/reference/replicated-cli-cluster-shell).
215217

216218
1. Verify that you can interact with the cluster through kubectl by running a command. For example:
217219

218220
```bash
219221
kubectl get ns
220222
```
221223

224+
1. Press Ctrl-D or type `exit` when done to end the shell and the connection to the server.
225+
222226
### Upgrade Clusters (kURL Only)
223227

224228
For kURL clusters provisioned with Compatibility Matrix, you can use the the `cluster upgrade` command to upgrade the version of the kURL installer specification used to provision the cluster. A recommended use case for the `cluster upgrade` command is for testing your application's compatibility with Kubernetes API resource version migrations after upgrade.

0 commit comments

Comments
 (0)