Setting up Kubernetes in AWS
In the following, we’re going to show you how to use
kubicorn to ramp up a Kubernetes cluster in AWS, use it and tear it down again.
As a prerequisite, you need to have
kubicorn installed. Since we don’t have binary releases yet, we assume you’ve got Go installed and simply do:
$ go get github.com/kubicorn/kubicorn
The first thing you will do now is to define the cluster resources.
For this, you need to select a certain profile. Of course, once you’re more familiar with
kubicorn, you can go ahead and extend existing profiles or create new ones.
In the following we’ll be using an existing profile called
aws, which is—surprise, surprise—a profile for a cluster in AWS.
Now execute the following command:
$ kubicorn create myfirstk8s --profile aws
kubicorn create did a good job by executing:
$ cat _state/myfirstk8s/cluster.yaml
Feel free to tweak the configuration to your liking here.
We’re now in a position to have the cluster resources defined, locally, based on the selected profile.
Next we will apply the so defined resources using the
apply command, but before we do that we’ll set up the access to AWS.
You might want to create a new IAM user for this with the following permissions:
If you would like to apply a more restrictive IAM policy to your AWS kubicorn user, take a look at the explicit list of actions used.
Next, you need to specify your AWS credentials to use - you can select one of the follwoing options
Environment Credentials - export the two environment variables
kubicorncan pick it up in the next step:
$ export AWS_ACCESS_KEY_ID=*************** $ export AWS_SECRET_ACCESS_KEY=*****************************************
Shared Credentials file - The
~/.aws/credentialsfile stores your credentials based on a profile name. You can specify the profile using the
--aws-profileflag or the
AWS_PROFILEenvironment variable, otherwise the
defaultprofile will be used.
EC2 Instance Role Credentials - Use EC2 Instance Role to assign credentials to application running on an EC2 instance.
Also, make sure that the public SSH key for your AWS account is called
id_rsa.pub, which is the default in above profile:
$ ls -al ~/.ssh/id_rsa.pub -rw-------@ 1 mhausenblas staff 754B 20 Mar 04:03 /Users/mhausenblas/.ssh/id_rsa.pub
With the access set up, we can now apply the resources we defined in the first step. This actually creates resources in AWS. Up to now we’ve only been working locally.
$ kubicorn apply myfirstk8s
kubicorn will reconcile your intended state against the actual state in the cloud, thus creating a Kubernetes cluster.
kubectl configuration file (kubeconfig) will be created or appended for the cluster on your local filesystem.
You can now
kubectl get nodes and verify that Kubernetes 1.7.0 is now running.
You can also
ssh into your instances using the example command found in the output from
To delete your cluster run:
$ kubicorn delete myfirstk8s
Congratulations, you’re an official
kubicorn user now and might want to dive deeper,
for example, learning how to define your own profiles.