Complete the before deploying the Azure Arc-enabled Kubernetes agent. Once the agent is deployed, it starts the Azure Arc registration of Kubernetes cluster using Azure CLI. The Azure CLI uses HELM to deploy the agent HELM charts on the cluster. The cluster nodes pull the images that are required to create the agent in the Azure-Arc namespace. The cluster nodes establish the outbound communication to the Microsoft Container Registry.
Perform the following steps to deploy the agent on a PowerFlex based Kubernetes cluster:
Run the following command to install the Azure Arc Kubernetes agent into the Kubernetes cluster:
[***@azurevm1 ~]# az connectedk8s connect --name AzureArcTest1 --resource-group AzureArcTest
Ensure that the required pods are created under azure-arc namespace and all the pods are in Running status to confirm that the agent is deployed successfully.
[****@azurevm1 ~]# kubectl get pods -n azure-arc
NAME READY STATUS RESTARTS AGE
cluster-metadata-operator-7cff574c4f-brrjz 2/2 Running 0 23m
clusterconnect-agent-6dfd867c68-pg56t 3/3 Running 0 23m
clusteridentityoperator-fd498bf96-bvf6p 2/2 Running 0 23m
config-agent-5ff6c457df-7qptz 2/2 Running 0 23m
controller-manager-8676dcdc6-n87hx 2/2 Running 0 23m
extension-manager-675b47d497-c78wb 2/2 Running 0 23m
flux-logs-agent-6596f58c56-mchgf 1/1 Running 0 23m
kube-aad-proxy-79f7568dbd-l2cqn 2/2 Running 0 23m
metrics-agent-5b9b94754f-58v9x 2/2 Running 0 23m
resource-sync-agent-f8c7c6b6b-lm55p 2/2 Running 0 23m
Once all the Azure-Arc-enabled Kubernetes agent pods are in running state, the cluster is connected to the Azure-Arc. The connected Kubernetes cluster is listed under the resource group in the Azure portal.
Note: Azure Arc-enabled Kubernetes agent does not require inbound ports on firewall. The agent initiates the outbound communication by enabling egress endpoints. For more information, see the network requirement section from the . The data centers using outbound proxy server for SSL handshake must follow the steps for deploying the agent.