Feedback Edit

Azure Arc-enabled Kubernetes agent overview

  • Article
  • 2 minutes to read

Kubernetes can deploy containerized workloads consistently on hybrid and multi-cloud environments. Azure Arc-enabled Kubernetes provides a centralized, consistent control plane to manage policy, governance, and security across Kubernetes clusters on these heterogenous environments.

This article provides an overview of the Azure Arc agents deployed on the Kubernetes clusters when connecting them to Azure Arc.

Deploy agents to your cluster

Most on-premises datacenters enforce strict network rules that prevent inbound communication on the network boundary firewall. Azure Arc-enabled Kubernetes works with these restrictions by not requiring inbound ports on the firewall. Azure Arc agents only require outbound communication to a set list of network endpoints.

Diagram showing an architectural overview of the Azure Arc-enabled Kubernetes agents.

The following high-level steps are involved in connecting a Kubernetes cluster to Azure Arc:

  1. Create a Kubernetes cluster on your choice of infrastructure (VMware vSphere, Amazon Web Services, Google Cloud Platform, etc.).

    Note

    Azure Arc-enabled Kubernetes currently only supports attaching existing Kubernetes clusters to Azure Arc. You must create the cluster before you connect it to Azure Arc.

  2. Start the Azure Arc registration for your cluster.

    • The agent Helm chart is deployed on the cluster.

    • The cluster nodes initiate an outbound communication to the Microsoft Container Registry, pulling the images needed to create the following agents in the azure-arc namespace:

      Agent Description
      deployment.apps/clusteridentityoperator Azure Arc-enabled Kubernetes currently supports only system assigned identities. clusteridentityoperator initiates the first outbound communication. This first communication fetches the Managed Service Identity (MSI) certificate used by other agents for communication with Azure.
      deployment.apps/config-agent Watches the connected cluster for source control configuration resources applied on the cluster. Updates the compliance state.
      deployment.apps/controller-manager An operator of operators that orchestrates interactions between Azure Arc components.
      deployment.apps/metrics-agent Collects metrics of other Arc agents to verify optimal performance.
      deployment.apps/cluster-metadata-operator Gathers cluster metadata, including cluster version, node count, and Azure Arc agent version.
      deployment.apps/resource-sync-agent Syncs the above-mentioned cluster metadata to Azure.
      deployment.apps/flux-logs-agent Collects logs from the flux operators deployed as a part of source control configuration.
      deployment.apps/extension-manager Installs and manages lifecycle of extension helm charts
      deployment.apps/kube-aad-proxy Used for authentication of requests sent to the cluster using Cluster Connect.
      deployment.apps/clusterconnect-agent Reverse proxy agent that enables the Cluster Connect feature to provide access to apiserver of the cluster. Optional component deployed only if the Cluster Connect feature is enabled.
      deployment.apps/guard Authentication and authorization webhook server used for Azure Active Directory (Azure AD) RBAC. Optional component deployed only if Azure RBAC is enabled on the cluster.

  3. Once all the Azure Arc-enabled Kubernetes agent pods are in Running state, verify that your cluster is connected to Azure Arc. You should see:

    • An Azure Arc-enabled Kubernetes resource in Azure Resource Manager. Azure tracks this resource as a projection of the customer-managed Kubernetes cluster, not the actual Kubernetes cluster itself.
    • Cluster metadata (such as Kubernetes version, agent version, and number of nodes) appearing on the Azure Arc-enabled Kubernetes resource as metadata.

Next steps