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: articles/operator-nexus/howto-kubernetes-cluster-connect.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,8 +70,6 @@ Once you are connected to a cluster via Arc for Kuberentes, you can connect to i
70
70
71
71
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, while in connected mode. 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.
72
72
73
-
To use `az arc ssh`, users need to manually connect the cluster VMs to Arc by creating a service principal (SP) with the 'Azure Connected Machine Onboarding' role. For more detailed steps on how to connect an Azure Operator Nexus Kubernetes cluster node to Arc, refer to the [how to guide](./howto-monitor-naks-cluster.md#monitor-nexus-kubernetes-cluster--vm-layer).
Copy file name to clipboardExpand all lines: articles/operator-nexus/howto-monitor-naks-cluster.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,7 +53,7 @@ The following resources provide you with support:
53
53
[!INCLUDE [dcr.sh](./includes/dcr.md)]
54
54
-`assign.sh`: use the script to create a policy to associate the DCR with all Arc-enabled servers in a resource group
55
55
[!INCLUDE [assign.sh](./includes/assign.md)]
56
-
-`install.sh`: Arc-enable Nexus Kubernetes cluster VMs and install Azure Monitoring Agent on each VM
56
+
-`install.sh`: Install Azure Monitoring Agent on each VM to collect monitoring data from Azure Virtual Machines.
57
57
[!INCLUDE [install.sh](./includes/install.md)]
58
58
59
59
### Prerequisites-VM
@@ -169,12 +169,13 @@ For convenience, the provided **`assign.sh`** script assigns the built-in policy
169
169
./assign.sh
170
170
```
171
171
172
-
#### Connect Arc-enabled servers and install Azure monitoring agent
172
+
#### Install Azure monitoring agent
173
173
174
-
Use the included **`install.sh`** script to Arc-enroll all server VMs that represent the nodes of the Nexus Kubernetes cluster.
175
-
This script creates a Kubernetes daemonSet on the Nexus Kubernetes cluster.
176
-
It deploys a pod to each cluster node, connecting each VM to Arc-enabled servers and installing the Azure Monitoring Agent (AMA).
174
+
Use the included **`install.sh`** which creates a Kubernetes daemonSet on the Nexus Kubernetes cluster.
175
+
It deploys a pod to each cluster node and installs the Azure Monitoring Agent (AMA).
177
176
The `daemonSet` also includes a liveness probe that monitors the server connection and AMA processes.
177
+
> [!NOTE]
178
+
> To install Azure Monitoring Agent, you must first Arc connect the Nexus Kubernetes cluster VMs. This process is automated if you are using the latest version bundle. However, if the version bundle you use does not support cluster VM Arc enrollment by default, you will need to upgrade your cluster to the latest version bundle. For more information about the version bundle, please refer [Nexus Kubernetes cluster supported versions](reference-nexus-kubernetes-cluster-supported-versions.md)
178
179
179
180
1. Set the environment as specified in [Environment Setup](#environment-setup). Set the current `kubeconfig` context for the Nexus Kubernetes cluster VMs.
180
181
2. Permit `Kubectl` access to the Nexus Kubernetes cluster.
@@ -191,7 +192,6 @@ kubectl logs <podname>
191
192
```
192
193
193
194
On completion, the system logs the message "Server monitoring configured successfully".
194
-
At that point, the Arc-enabled servers appear as resources within the selected resource group.
195
195
196
196
> [!NOTE]
197
197
> Associate these connected servers to the [DCR](#associate-arc-enabled-server-resources-to-dcr).
@@ -277,7 +277,7 @@ Validate the successful deployment of monitoring agents’ enablement on Nexus K
277
277
az k8s-extension show --name azuremonitor-containers \
if grep "Could not arc enroll server" "\${WORKDIR}"/setup_arc_for_servers.out > /dev/null; then
550
-
exit 1
551
-
fi
552
-
553
-
/usr/bin/azcmagent config set incomingconnections.ports 22
554
-
/usr/bin/azcmagent config set extensions.allowlist Microsoft.Azure.Monitor/AzureMonitorLinuxAgent,Microsoft.Azure.AzureDefenderForServers/MDE.Linux,Microsoft.Azure.ActiveDirectory/AADSSHLoginForLinux
555
-
556
406
if [ "\${INSTALL_AZURE_MONITOR_AGENT}" = "true" ]; then
0 commit comments