Installing Kubernetes with Kubespray on AWS

With Ansible playbooks, Kubespray provides added flexibility in deploying Kubernetes clusters.

Kubespray is a composition of Ansible playbooks aimed at providing users with a flexible method of deploying a production-grade Kubernetes cluster. However, deploying Kubernetes with Kubespray can get tricky if you are not too familiar with the technology.

In this tutorial, we will show how to deploy Kubernetes with Kubespray on AWS.


Installing dependencies

Before deploying, we will need a virtual machine (hereinafter Jumpbox) with all the software dependencies installed. Check the list of distributions supported by Kubespray and deploy the Jumpbox with one of these distributions. Make sure to have the latest version of Python installed. Next, the dependencies from requirements.text in Kubespray’s GitHub repo must be installed.

sudo pip install -r requirements.txt

Lastly, install Terraform by HashiCorp. Simply download the latest version of Terraform according to your distribution and install it to your /usr/local/bin folder. For example:

sudo mv terraform /usr/local/bin/


Building a cloud infrastructure with Terraform

Since Kubespray does not automatically create virtual machines, we need to use Terraform to help provision our infrastructure. To start, we create an SSH key pair for Ansible on AWS.

An example of a key pair being created

The next step is to clone the Kubespray repository into our jumpbox.

git clone

We then enter the cloned directory and copy the credentials.

cd kubespray/contrib/terraform/aws/
cp credentials.tfvars.example credentials.tfvars

After copying, fill out credentials.tfvars with our AWS credentials.

vim credentials.tfvars

In this case, the AWS credentials were as follows.

#AWS Access Key
#AWS Secret Key
#EC2 SSH Key Name
AWS_SSH_KEY_NAME = "Altoros-kubespray"
#AWS Region
AWS_DEFAULT_REGION = "us-east-2"

Next, we edit terraform.tfvars in order to customize our infrastructure.

vim terraform.tfvars

Below is an example configuration.

#Global Vars
aws_cluster_name = "altoros-cluster"

#VPC Vars
aws_vpc_cidr_block       = ""
aws_cidr_subnets_private = ["", ""]
aws_cidr_subnets_public  = ["", ""]

#Bastion Host
aws_bastion_size = "t2.medium"

#Kubernetes Cluster

aws_kube_master_num  = 3
aws_kube_master_size = "t2.medium"

aws_etcd_num  = 3
aws_etcd_size = "t2.medium"

aws_kube_worker_num  = 4
aws_kube_worker_size = "t2.medium"

#Settings AWS ELB

aws_elb_api_port                = 6443
k8s_secure_api_port             = 6443
kube_insecure_apiserver_address = ""

default_tags = {
  #  Env = "devtest"
  #  Product = "kubernetes"

inventory_file = "../../../inventory/hosts"

Next, initialize Terraform and run terraform plan to see any changes required for the infrastructure.

terraform init
terraform plan -out mysuperplan -var-file=credentials.tfvars

After, apply the plan that was just created. This begins deploying the infrastructure and may take a few minutes.

terraform apply “mysuperplan”

Once deployed, we can check out the infrastructure in our AWS dashboard.

Deployed instances shown in the AWS dashboard


Microservices Architecture

Deploying a cluster with Kubespray

With the infrastructure provisioned, we can begin to deploy a Kubernetes cluster using Ansible. Start off by entering the Kubespray directory and use the Ansible inventory file created by Terraform.

cd ~/kubespray
cat inventory/hosts

Next, load the SSH keys, which were created in AWS earlier on. First, create a file (in our case, it will be located at ~/.ssh/Altoros/kubespray.pem) and paste the private part of the key created at AWS there.

cat “” > ~/.ssh/Altoros/kubespray.pem
eval $(ssh-agent)
ssh-add -D
ssh-add ~/.ssh/Altoros/kubespray.pem

Once the SSH keys are loaded, we can now deploy a cluster using Ansible playbooks. This takes roughly 20 minutes.

ansible-playbook -i ./inventory/hosts ./cluster.yml -e ansible_user=core -b --become-user=root --flush-cache


Configuring access to the cluster

Now that the cluster has been deployed, we can configure who has access to it. First, find the IP address of the first master.

cat inventory/hosts

After identifying the IP address, we can SSH to the first master.

ssh  -F ssh-bastion.conf core@

Once connected, we are set as a core user. Switch to the root user and copy the kubectl config located in the root home folder.

sudo ~s
cd ~
cd .kube
cat config

Highlight and copy the kubectl config as shown in the following image.

Example kubectl config

Return to the jumpbox and go to kube/config.

vim ~/.kube/config

Paste the copied kubectl config here.

Copying kubectl config

Next, copy the URL of the load balancer from the inventory file. In our case, the URL is Paste this URL into the server parameter in kubectl config. Do not overwrite the port.


Running test deployments

After configuring access to the cluster, we can check on our cluster.

kubectl get nodes
kubectl cluster-info

Node and cluster details will be shown in the console.

Cluster and node details

With the cluster ready, we can run a test deployment.

kubectl create deployment nginx --image=nginx
kubectl get pods
kubectl get deployments

Entering this commands should deploy NGINX and also return the status of the pods and deployments.

A successful test deployment

With this, we have successfully provisioned our cloud infrastructure with Terraform. We then deployed a Kubernetes cluster using Kubespray. We also configured access to the cluster and were finally able to run test deployments.

More on Kubespray can be found in its GitHub repository, as well as in the project’s official documentation.


Want details? Watch the video!

The video demonstrates how to deploy Kubernetes clusters on AWS using Kubespray.


Further reading


The post was written by Arsenii Petrovich, Viachaslau Matsukevich, and Carlo Gutierrez;
edited by Sophia Turol and Alex Khizhniak.
Interested in how to effectively use the Kuberneres CLI to manage your deployment? Download our kubectl cheat sheet!
  • 4