Creating Konvoy Clusters on Azure

A guide for creating Konvoy clusters on Azure

Before you begin

Configured Azure Infrastructure Provider

Simplified Cluster Creation on Azure

Add Cluster Options

From the Add Cluster menu, select the Create Konvoy Cluster and provide some basic cluster details:

  • Workspace: The workspace where this cluster belongs.
  • Kubernetes Version: The initial version of Kubernetes to install on the cluster.
  • Name: A display name for referencing the cluster.

Select the preconfigured Azure Infrastructure Provider to display the options specific to Azure.

  • Region: Select the datacenter region to show selectable Availability Zones. Azure maintains multiple datacenters per region.
  • Resource Group: The resource group where the Azure assets are assigned.
  • VNET Name: The virtual network name in which to create this cluster.
  • VNET Route Table: Azure automatically routes traffic between Azure subnets, virtual networks, and on-premises networks. To change any of Azure’s default routing, create a route table.
  • Configure Node Pools: Specify pools of nodes, their size, and quantity. The suggested default is a control plane pool containing 3 Standard_DS3_v2 nodes and a worker pool containing 4 Standard_DS3_v2 nodes. You can also specify labels, node taints, and subnet ID’s as part of each pool.
  • Add Infrastructure Provider Tags: Specify tags on all resources created in your infrastructure provider for this cluster. You can add up to 10 tags in this form. Different infrastructure providers have varying restrictions on their tags. See the Azure Tags User Guide for more information on using tags in Azure.
  • Add Labels: By default, your cluster has some labels that reflect the infrastructure provider provisioning. For example, in Azure your cluster may be labelled with the datacenter region as well as provider: azure. Cluster labels are matched to the selectors created for projects. Changing a cluster label may add or remove the cluster from projects.

Select Continue to begin provisioning the Konvoy cluster.