Skip to content
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Go to file
Cannot retrieve contributors at this time

Using Vagrant

There is a Vagrantfile in the root of this repository, which will provision a Vagrant box that contains all the necessary tools needed to conduct the labs. You will need to have the following installed on your local host:

Clone the Repository

git clone
cd getting-to-know-k8s

AWS API Credentials

Kops, which we will be using to create Kubernetes clusters, requires you to have AWS API credentials configured.

You can use your existing AWS user account or you can choose to create a dedicated user account for Kops.

Use an existing AWS user account

If you are using your existing AWS user account, you must have at a minimum the following IAM policies attached to it (or you can use the AdministratorAccess policy which includes all of these permissions):


Create a dedicated user account for Kops

To create a dedicated user account for Kops, you can either use the management console or the AWS CLI:

aws iam create-group --group-name kops

export arns="

for arn in $arns; do aws iam attach-group-policy --policy-arn "$arn" --group-name kops; done

aws iam create-user --user-name kops

aws iam add-user-to-group --user-name kops --group-name kops

aws iam create-access-key --user-name kops

You should record the values for SecretAccessKey and AccessKeyID in the returned JSON output, which are the AWS API credentials.

Set the Required Environment Variables

Before starting the Vagrant box, you need to set the environment variables below with the AWS API credentials of the AWS user account you will be using:

export AWS_ACCESS_KEY_ID="AWS Access Key ID"
export AWS_SECRET_ACCESS_KEY="AWS Secret Access Key"

Vagrant will automatically apply these environment variables to the Vagrant box during start-up.

If you are not familiar with how to retrieve these values for your existing AWS user account, refer to the AWS documentation.

Verify SSH Key Paths in Vagrantfile

Kops also requires a SSH public key file, which is used to create an AWS EC2 key pair for AWS instances that are created when creating a cluster.

If you don't have a SSH key available, refer to this tutorial from GitHub on how to create one.

If your existing SSH key files are not located in the default location (~/.ssh/ & ~/.ssh/id_rsa), you will need to update the following lines in the Vagrantfile before starting the Vagrant box:

aws_keypair_pub_key_path = "~/.ssh/"
aws_keypair_pri_key_path = "~/.ssh/id_rsa"

Vagrant will automatically copy these files to the Vagrant box during start-up.

Verify Versions of Tools

You can change the versions of the tools that will be installed on the Vagrant box. To do so, update the following variables in the /scripts/ file before starting the Vagrant box:

# Vagrant installation variables
export KUBECTL_VERSION="1.7.6"
export KUBEFED_VERSION="1.7.6"
export KOPS_VERSION="1.7.0"
export HUGO_VERSION="0.27.1"
export TERRAFORM_VERSION="0.10.6"

Start the Vagrant Box and Connect

From the root of the repository:

vagrant up
vagrant ssh

Enjoy the Labs

You are ready to proceed with the labs.