Azure Arc Enabled Kubernetes for Multicloud

Chapter 4. Using Azure Arc Enabled Kubernetes

In this final chapter, let’s begin by exploring the architecture involved with Azure Arc enabled Kubernetes and what it takes to onboard, monitor, and use RBAC with an Azure Arc projected Kubernetes cluster. We’ll also dive into how to deploy an app to an Azure Arc projected Kubernetes cluster using GitOps.

Azure Arc Enabled Kubernetes Architecture and Agents

Azure Arc enabled Kubernetes is essentially a PaaS running in Azure. The architecture for the service itself is abstracted away. Azure Arc enabled Kubernetes architecture generally consists of some Azure services, resources, tools, and agents and a number of Deployments and Pods running on the projected Kubernetes cluster. Let’s unpack all of this to dive deeper into what the architecture and agent entail.

First, you’ll need a Kubernetes cluster running either in Azure or outside of Azure. This can be AKS; GKE; EKS; Kubernetes running on VMs in Azure, AWS, GCP, on-premises, etc.; Rancher K3s; or even Kubernetes running on an edge device. This becomes your projected Kubernetes cluster in Azure Arc enabled Kubernetes.

You’ll need the kubeconfig file to access the cluster and cluster-admin role on the projected Kubernetes cluster. This will give the access needed to deploy the Arc agents.

You’ll need the Azure command-line interface (Azure CLI) version 2.3 or higher. This is needed to install the Azure Arc enabled Kubernetes interface extensions and used to perform registration ...