Installing Kubernetes with Ansible on AWS

This article explains how to install Kubernetes using Ansible on AWS's Ubuntu 20.04 computing clusters.

A relevant article can be found here: Create Multi-Node Kubernetes using Ansible inside AWS EC2 Instance.

For installing Kuberenetes onto Vagrant configurations, please refer to this page: Kubernetes setup using Ansible and Vagrant.

Set up at least two machines on AWS

The first task is to create two EC2 instances that matches Kubernetes Cluster minimal configuration:

The master node must have at least 2 CPU cores, 2 Gb of memory.
The worker node (slave) should have at least 1 CPU core and 2 Gb of memory.

Set the right Security Groups

{{#lst:Input/K8s Installation/Security Groups|Security Groups}}

Ideally, one could first create a Security Group, and name it K8s Sec Grp, then, just create two or more instances of EC2, and select the said security group during the creation cycle.

Use the same Signature File

When creating these instances, make sure that you create or select the same Identity file (.pem file) for all instances of the same cluster. This will significantly reduce the complexity of installation.

Make sure Ansible is installed

Install Ansible on the machine that will run Ansible to install the cluster. You may follow this procedure: Installing Ansible. If you already installed Python 3.0 and pip3, launch the following instruction in your terminal should work:

 pip3 install ansible

Set up Ansible Inventory file

It is necessary to set up the inventory files for Ansible. See the following examples:

For inventory file, one should provide a list of machines, and a list of variables (vars) that applies to all these machines. In our case, we want to access all these machines using the same ansible_user: ubuntu.

m1.xlp.pub
w1.xlp.pub
[all:vars]
ansible_user=ubuntu

Set up Ansible Configuration file

One must also create the ansible.cfg files in the current working directory. See the following examples:

[defaults]
inventory = inventory
private_key_file = ~/.ssh/ansible.pem

Test to see if Ansible can access the machines

In the following instruction, all indicates running the instruction set on all machines, where -m ping, indicates that this instruction will run the module, ping on all the machines.

ansible all -m ping

For a more elaborate instruction, see Ansible/First Instruction. Other useful instructions to test if Ansible is running properly: Ansible/Useful Instructions.

Make changes to machines using Ansible

If you have certain password that you can key-in during an interactive session, you may use the following instruction. Note that if the user already is in the administrator group, you can ignore the --ask-become-pass part of the statement. By supplying the --ask-become-pass option, you will be asked to enter a password.

ansible all -m apt -a update_cache=true --become --ask-become-pass