Edit

Share via


Network connectivity for Azure Arc-enabled Kubernetes

Arc-enabled Kubernetes supports fully connected and semi-connected modes to onboard and manage Kubernetes clusters with Azure Arc's control plane. Azure Arc-enabled Kubernetes agents connect to Azure Arc endpoints to exchange metadata. They use pull and push methods from Kubernetes clusters.

This article covers tips to connect Arc-enabled Kubernetes clusters to the Azure control plane. It applies to on-premises and other cloud setups.

Architecture

The following diagram shows an Azure Arc-enabled Kubernetes network layout that supports fully connected and semi-connected modes.

A diagram showing Azure Arc-enabled Kubernetes network architecture.

The following diagram shows a network layout that lets you reach clusters from any location. It uses the Azure Arc-enabled Kubernetes Cluster Connect feature.

A diagram showing Azure Arc-enabled Kubernetes Cluster Connect network architecture.

Design considerations

  • Review the network topology and connectivity design area of the Azure landing zones. Check how Azure Arc-enabled Kubernetes affects your network model.
  • Review the network requirements for Azure Arc-enabled Kubernetes. Learn how clusters connect to Azure from on-premises networks or other cloud providers.
  • Balance your org's security and compliance needs with the benefits of Azure Arc-enabled Kubernetes. Then pick fully connected mode or semi-connected mode for your setup.
  • Decide if you want to use public or private endpoints for Azure Log Analytics workspaces. Choose between ExpressRoute or VPN and the internet.
  • Decide if you want to use public or private endpoints for Azure Key Vaults. Choose between ExpressRoute or VPN and the internet.
  • Choose how to connect for Azure Arc-enabled Kubernetes cluster management. Azure Arc-enabled Kubernetes clusters support cluster management from any network. For tips on network-independent cluster management, see Identity and Access Management.
  • Consider using the Cluster Connect feature. It removes the need to open inbound network ports. It allows only outbound traffic to Azure Arc services.
  • Your on-premises or multicloud firewalls or proxy servers might do TLS inspection of outbound traffic. They might also run network intrusion detection and prevention (IDPS). If so, decide if you should exempt Azure Arc-enabled Kubernetes endpoints. These firewalls or proxy servers might not trust some server certificates.

Design recommendations

Next steps

For more info on your hybrid and multicloud journey, see these articles: