Skip to content

Commit 5ba71d0

Browse files
committed
Fixed few issues
1 parent d46302e commit 5ba71d0

File tree

1 file changed

+9
-5
lines changed

1 file changed

+9
-5
lines changed

articles/operator-nexus/howto-kubernetes-cluster-connect.md

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -17,18 +17,19 @@ Throughout the lifecycle of your Azure Operator Nexus Kubernetes cluster, you ev
1717

1818
* An Azure Operator Nexus Kubernetes cluster deployed in a resource group in your Azure subscription.
1919
* SSH private key for the cluster nodes.
20-
* To SSH using the node IP address, it's necessary to have a jumpbox VM deployed within the same virtual network as the cluster nodes.
20+
* To SSH using the node IP address, you must deploy a jumpbox VM on the same Container Network Interface (CNI) network as the cluster nodes.
2121

2222
## Access nodes using the Kubernetes API
2323

2424
This method requires usage of `kubectl debug` command.
2525

26-
### Azure Arc for Kubernetes
26+
### Access to Kubernetes API via Azure Arc for Kubernetes
2727

2828
[!INCLUDE [quickstart-cluster-connect](./includes/kubernetes-cluster/cluster-connect.md)]
2929

3030
### Access to cluster nodes via Azure Arc for Kubernetes
31-
Once you're connected to a cluster via Arc for Kubernetes, you can connect to individual Kubernetes Node using the `kubectl debug` command to run a privileged container on your node.
31+
32+
Once you're connected to a cluster via Arc for Kubernetes, you can connect to individual Kubernetes node using the `kubectl debug` command to run a privileged container on your node.
3233

3334
1. List the nodes in your Nexus Kubernetes cluster:
3435

@@ -49,7 +50,7 @@ Once you're connected to a cluster via Arc for Kubernetes, you can connect to in
4950
root [ / ]#
5051
```
5152

52-
This privileged container gives access to the node. Execute commands on the baremetal host machine by running `chroot /host` at the command line.
53+
This privileged container gives access to the node. Execute commands on the cluster node by running `chroot /host` at the command line.
5354

5455
3. When you're done with a debugging pod, enter the `exit` command to end the interactive shell session. After exiting the shell, make sure to delete the pod:
5556

@@ -59,7 +60,10 @@ Once you're connected to a cluster via Arc for Kubernetes, you can connect to in
5960

6061
## Access to cluster nodes via Azure Arc for servers
6162

62-
The `az ssh arc` command allows users to remotely access a cluster VM that has been connected to Azure Arc. This method is a secure way to SSH into the cluster node directly from the command line. Once the cluster VM has been registered with Azure Arc, the `az ssh arc` command can be used to manage the machine remotely, making it a quick and efficient method for remote management.
63+
The `az ssh arc` command allows users to remotely access a cluster VM that has been connected to Azure Arc. This method is a secure way to SSH into the cluster node directly from the command line, making it a quick and efficient method for remote management.
64+
65+
> [!NOTE]
66+
> Operator Nexus Kubernetes cluster nodes are Arc connected servers by default.
6367

6468
1. Set the required variables. Replace the placeholders with the actual values relevant to your Azure environment and Nexus Kubernetes cluster.
6569

0 commit comments

Comments
 (0)