Create the Azure Arc data controller

Note

As a preview feature, the technology presented in this article is subject to Supplemental Terms of Use for Microsoft Azure Previews.

For current limitations, check the known issues in the release notes.

Overview of creating the Azure Arc data controller

Azure Arc enabled data services can be created on multiple different types of Kubernetes clusters and managed Kubernetes services using multiple different approaches.

Currently, the supported list of Kubernetes services and distributions are the following:

  • Azure Kubernetes Service (AKS)
  • Azure Kubernetes Service Engine (AKS Engine) on Azure Stack
  • Azure Kubernetes Service on Azure Stack HCI
  • Azure RedHat OpenShift (ARO)
  • OpenShift Container Platform (OCP)
  • AWS Elastic Kubernetes Service (EKS)
  • Google Cloud Kubernetes Engine (GKE)
  • Open source, upstream Kubernetes typically deployed using kubeadm

Important

  • The minimum supported version of Kubernetes is v1.17. See Known issues for additional information.
  • The minimum supported version of OCP is 4.3.
  • See the connectivity requirements to understand what connectivity is required between your environment and Azure.
  • See the storage configuration guidance to understand the details of how to configure your persistent storage.
  • If you are using Azure Kubernetes Service, your cluster's worker node VM size should be at least Standard_D8s_v3 and use premium disks. The cluster should not span multiple availability zones.
  • If you are using another Kubernetes distribution or service, you should ensure that you have a minimum node size of 8 GB RAM and 4 cores and a sum total capacity of 32 GB RAM available across all of your Kubernetes nodes. For example, you could have 1 node at 32 GB RAM and 4 cores or you could have 2 nodes with 16GB RAM and 4 cores each.

Note

If you are using Red Hat OpenShift Container Platform on Azure, it is recommended to use the latest available version.

Depending on the option you choose, certain tools will be required, but it is recommended to install all the client tools before you begin to create the Azure Arc data controller.

Regardless of the option you choose, during the creation process you will need to provide the following information:

  • Data controller name - A descriptive name for your data controller - e.g. "Production data controller", "Seattle data controller".
  • Data controller username - Any username for the data controller administrator user.
  • Data controller password - A password for the data controller administrator user.
  • Name of your Kubernetes namespace - the name of the Kubernetes namespace that you want to create the data controller in.
  • Connectivity mode - Connectivity mode determines the degree of connectivity from your Azure Arc enabled data services environment to Azure. Preview currently only supports indirectly connected and directly connected modes. For information, see connectivity mode.
  • Azure subscription ID - The Azure subscription GUID for where you want the data controller resource in Azure to be created.
  • Azure resource group name - The name of the resource group where you want the data controller resource in Azure to be created.
  • Azure location - The Azure location where the data controller resource metadata will be stored in Azure. For a list of available regions, see Azure global infrastructure / Products by region.

Next steps

There are multiple options for creating the Azure Arc data controller:

Just want to try things out?
Get started quickly with Azure Arc Jumpstart on Azure Kubernetes Service (AKS), AWS Elastic Kubernetes Service (EKS), Google Cloud Kubernetes Engine (GKE) or in an Azure VM!