Step 1.2: Configuring the VM

Configuring the DNS of the VM

Note: Configuring the DNS on each VM is optional if you are deploying a multi-node HA-ready production setup behind a load balancer.

1. Select the value of the DNS Name to set the DNS name of the machine.
   
   

   

   
   
2. In the VM IP configuration window displayed, set the DNS name label:
   
   

   

   
   
3. Select Save.

Testing the Connection to the VM

Test the connection to the VM using SSH. Request Just In Time access if needed.

• To connect to the machine using SSH, follow the Azure instructions.

• Alternatively, you can connect to the machine on your terminal using SSH:

  # If you set a password the command is: 
  ssh <user>@<dns_of_vm> 
  # If you used an ssh key: 
  ssh -i <.\Path\To\myKey1.pem> <user>@<dns_of_vm>

Partitioning the Disk

Log in to the machine via SSH using the following commands:

• If you set a password:

  ssh <user>@<dns_of_vm>

• If you used an SSH key:

  ssh -i <.\Path\To\myKey1.pem> <user>@<dns_of_vm>

Identifying the Device Name for the Disk in Azure

Note:

The disk device name is different from the disk name. You will need the disk device name when configuring the disk.

To configure the disk for installation, see the following:

• Configuring the disk for a single-node evaluation setup
• Configuring the disk for a multi-node HA-ready production setup

1. In the Disks tab of every VM in the Azure portal, you can find the LUN (Logical Unit Number) corresponding to each attached disk.
   
   

   

   
   
2. Run the following command to identify the disk device name, where LUN=<lun_value> as identified in the Azure portal:

   LUN=<lun_value>
   echo "/dev/$(tree /dev/disk/azure/ | grep -w "\slun${LUN}\s" | awk -F/ '{print $NF}')"

Multi-node Only: Configuring Additional Ports

These additional inbound ports are needed only for multi-node HA-ready production installations. Add them to all VMs.

Port	Protocol	Source	Destination	Purpose
443	TCP	Any	Any	https traffic
2379	TCP	VirtualNetwork	VirtualNetwork	etcd client port
2380	TCP	VirtualNetwork	VirtualNetwork	etcd peer port
6443	TCP	Any	Any	Kubernetes API
8472	UDP	VirtualNetwork	VirtualNetwork	Flannel
9345	TCP	Any	Any	Kubernetes API
10250	TCP	VirtualNetwork	VirtualNetwork	kubelet
30071	TCP	VirtualNetwork	VirtualNetwork	NodePort

Opening TCP ports on an Azure VM for multi-node installations

Create new inbound networking rules for the ports needed over TCP protocol.

1. Select the VM’s Overview tab, then select the Networking tab:
   
   

   

   
   
2. Select Add inbound port rule.
   
   

   

   
   
3. Change the fields as required:
   • Destination port range
   • Protocol

   • Name

     You can add as a comma-separated list with ranges:

     
     

     

     
     
4. Add all the TCP in one inbound rule as previously shown, and the UDP in a separate one. For the UDP, add +1 to the priority.
   
   

   

   
   
5. And select Add.