Getting started with Kubernetes using Ansible

Some of you will recall that I had previously written a set of SaltStack states to provision a bare metal Kubernetes cluster.  The idea was that you could use it to quickly deploy (and redeploy) a Kubernetes lab so you could get more familiar with the project and do some lab work on a real cluster.  Kubernetes is a fast moving project and I think you’ll find that those states likely no longer work with all of the changes that have been introduced into Kubernetes.  As I looked to refresh the posts I found that I was now much more comfortable with Ansible than I was with SaltStack so this time around I decided to write the automation using Ansible (I did also update the SaltStack version but I’ll be focusing on Ansible going forward).

However – before I could automate the configuration I had to remind myself how to do the install manually. To do this, I leaned heavily on Kelsey Hightower’s ‘Kubernetes the hard way‘ instructions.  These are a great resource and if you haven’t installed a cluster manually before I suggest you do that before attempting to automate an install.  You’ll find that the Ansible role I wrote VERY closely mimics Kelsey’s directions so if you’re looking to understand what the role does I’d suggest reading through Kelsey’s guide.  A big thank you to him for publishing it!

So let’s get started…

This is what my small lab looks like.  A couple of brief notes on the base setup…

  • All hosts are running a fresh install of Ubuntu 16.04.  The only options selected for package installation were for the OpenSSH server so we could access the servers via SSH
  • The servers all have static IPs as shown in the diagram and a default gateway as listed on the L3 gateway
  • All servers reference a local DNS server (not pictured) and are resolvable in the local ‘interubernet.local’ domain (ex: ubuntu-1.interubernet.local).  They are also reachable via short name since the configuration also specifies a search domain (interubernet.local).
  • All of these servers can reach the internet through the L3 gateway and use the aforementioned DNS server to resolve public names.  This is important since the nodes will download binaries from the internet during cluster configuration.
  • In my example – I’m using 5 hosts.  You don’t need 5 but I think you’d want at least 3 so you could have 1 master and 2 minions but the role is configurable so you can have as many as you want
  • I’ll be using the first host (ubuntu-1) as both the Kubernetes master as well as the Ansible controller.  The remaining hosts will be Ansible clients and Kubernetes minions
  • The servers all have a user called ‘user’ which I’ll be using throughout the configuration

With that out of the way let’s get started.  The first thing we want to do is to get Ansible up and running.  To do that, we’ll start on the Ansible controller (ubuntu-1) by getting SSH prepped for Ansible.  The first thing we’ll do is generate an SSH key for our user (remember this is a new box, you might already have a key)…

To do this, we use the ‘ssh-keygen’ command to create a key for the user. In my case, I just hit enter to accept the defaults and to not set a password on the key (remember – this is a lab). Next we need to copy the public key to all of the servers that the Ansible controller needs to talk to. To perform the copy we’ll use the ‘ssh-copy-id’ command to move the key to all of the hosts…

Above I copied the key over for the user ‘user’ on the server ubuntu-5. You’ll need to do this for all 5 servers (including the master).  Now that’s in place make sure that the keys are working by trying to SSH directly into the servers…

While you’re in each server make sure that Python is installed on each host. Besides the above SSH setup – having Python installed is the only other requirement for the hosts to be able to communicate and work with the Ansible controller…

In my case Python wasn’t installed (these were really stripped down OS installs so that makes sense) but there’s a good chance your servers will already have Python. Once all of the clients are tested we can move on to install Ansible on the controller node. To do this we’ll use the following commands…

I wont bother showing the output since these are all pretty standard operations. Note that in addition to installing Ansible we also are installing Python PIP. Some of the Jinja templating I do with the playbook requires the Python netaddr library.  After you install Ansible and PIP take care of installing the netaddr package to get that out of the way…

Now we need to tell Ansible what hosts we’re working with. This is done by defining hosts in the ‘/etc/ansible/hosts’ file. The Kubernetes role I wrote expects two host groups. Once called ‘masters’ and once call ‘minions’. When you edit the host file for the first time there will likely be a series of comments with examples. To clean things up I like to delete all of the example comments and just add the two required groups. In the end my Ansible hosts file looks like this…

You’ll note that the ‘masters’ group is plural but at this time the role only supports defining a single master.

Now that we told Ansible what hosts it should talk to we can verify that Ansible can talk to them. To do that, run this command…

You should see a ‘pong’ result from each host indicating that it worked. Pretty easy right? Now we need to install the role. To do this we’ll create a new role directory called ‘kubernetes’ and then clone my repository into it like this…

Make sure you put the ‘.’ at the end of the git command otherwise git will create a new folder in the kubernetes directory to put all of the files in.  Once you’ve download the repository you need to update the variables that Ansible will use for the Kubernetes installation. To do that, you’ll need to edit roles variable file which should now be located at ‘/etc/ansible/roles/kubernetes/vars/main.yaml’. Let’s take a look at that file…

I’ve done my best to make ‘useful’ comments in here but there’s a lot more that needs to be explained (and will be in a future post) but for now you need to definitely pay attention to the following items…

  • The host_roles list needs to be updated to reflect your actual hosts.  You can add more or have less but the type of the host you define in this list needs to match what group its a member of in your Ansible hosts file.  That is, a minion type in the var file needs to be in the minion group in the Ansible host file.
  • Under cluster_info you need to make sure you pick two network that don’t overlap with your existing network.
    • For service_network_cidr pick an unused /24.  This wont ever get routed on your network but it should be unique.
    • For cluster_node_cidr pick a large network that you aren’t using (a /16 is ideal).  Kubernetes will allocate a /24 for each host out of this network to use for pods.  You WILL need to route this traffic on your L3 gateway but we’ll walk through how to do that once we get the cluster up and online.

Once the vars file is updated the last thing we need to do is tell Ansible what to do with the role. To do this, we’ll build a simple playbook that looks like this…

The playbook says “Run the role kubernetes on hosts in the masters and the minions group”.  Save the playbook as a YAML file somewhere on the system (in my case I just saved it in ~ as k8s_install.yaml). Now all we need to do is run it! To do that run this command…

Note the addition of the ‘–ask-become-pass’ parameter. When you run this command, Ansible will ask you for the sudo password to use on the hosts. Many of the tasks in the role require sudo access so this is required. An alternative to having to pass this parameter is to edit the sudoers file on each host and allow the user ‘user’ to perform passwordless sudo. However – using the parameter is just easier to get you up and running quickly.

Once you run the command Ansible will start doing it’s thing. The output is rather verbose and there will be lots of it…

If you encounter any failures using the role please contact me (or better yet open an issue in the repo on GitHub).  Once Ansible finishes running we should be able to check the status of the cluster almost immediately…

The component status should return a status of ‘Healthy’ for each component and the nodes should all move to a ‘Ready’ state.  The nodes will take a minute or two in order to transition from ‘NotReady’ to ‘Ready’ state so be patient. Once it’s up we need to work on setting up our network routing. As I mentioned above we need to route the network Kubernetes used for the pod networks to the appropriate hosts. To find which hosts got which network we can use this command which is pointed out in the ‘Kubernetes the hard way’ documentation…

Slick – ok. So now it’s up to us to make sure that each of those /24’s gets routed to each of those hosts. On my gateway, I want the routing to look like this…

Make sure you add the routes on your L3 gateway before you move on.  Once routing is in place we can deploy our first pods.  The first pod we’re going to deploy is kube-dns which is used by the cluster for name resolution.  The Ansible role already took care of placing the pod definition files for kube-dns on the controller for you, you just need to tell the cluster to run them…

As you can see there is both a service and a pod definition you need to install by passing the YAML file to the kubectl command with the ‘-f’ parameter. Once you’ve done that we can check to see the status of both the service and the pod…

If all went well you should see that each pod is running all three containers (denoted by the 3/3) and that the service is present.  At this point you’ve got yourself your very own Kubernetes cluster.  In the next post we’ll walk through deploying an example pod and step through how Kubernetes does networking.  Stay tuned!

  1. dIM’s avatar


    Does this set up employ High Availability?


    1. Jon Langemak’s avatar

      Definitely not. The build puts a single instance of all critical components on one server. This is best for the quick stand up of a lab environment but I plan on making the role more robust in the future.


    2. Radoslav Mitov’s avatar

      Hi Jon,
      I’m not sure but… after reproducing the lab from the example on the last step: creating kube-dns’s pods, my setup stuck on ContainerCreating:

      rado@ubu1:/var/lib/kubernetes/pod_defs$ kubectl –namespace=kube-system get pod
      kube-dns-v20-2501578361-7p3cj 0/3 ContainerCreating 0 5m
      kube-dns-v20-2501578361-lfskh 0/3 ContainerCreating 0 5m
      rado@ubu1:/var/lib/kubernetes/pod_defs$ kubectl describe

      I solved it by applying weave to the master node:
      kubectl apply -f



    3. Radoslav Mitov’s avatar

      Hi again Jon, Please delete my previous comment…


    4. DT’s avatar


      is autoscale enabled by this role ?


      1. Jon Langemak’s avatar

        Can you clarify what you mean by autoscale?


      2. dimgr’s avatar

        the ansible role finished ok with no errors but i get this
        ubuntu@ubuntu1:~$ kubectl get componentstatus
        The connection to the server localhost:8080 was refused – did you specify the right host or port?

        any tips.. ? thanks


        1. dimgr’s avatar


          can someone please help with the above error?


          1. Jon Langemak’s avatar

            Sorry for the delay – what does your configuration for kube-apiserver look like?


          2. Pascal’s avatar

            Thx for this awesome posts about docker and kubernetes.

            I tried this at home but get a few problems to the end:

            it seems to me that the minions didn’t get the correct pod networks. When executing “kubectl get nodes…” I get an error:

            “Error executing template: podCIDR is not found. Printing more information for debugging the template:”


            1. Pascal’s avatar

              Never mind. I found the comments in your git repository. 😉


              1. Jon Langemak’s avatar

                Anything I can do to make things more clear? Let me know!


              2. Adrian’s avatar

                Hello,I’m trying this on openstack machines (ip’s like 10.97.177….).
                The installation has finished with no error but when i try to check the etcd cluster it’s down
                kubectl get componentstatus
                controller-manager Healthy ok
                etcd-0 Unhealthy Get x509: certificate is valid for,, 10.97.177.xx, 10.97.177.xx, 10.97.177.xx, 10.97.177.xx, 10.97.177.xx, not
                scheduler Healthy ok

                What i’ve changed is:

                user from “user” to “ubuntu”; this is a sudoer
                IP’s and machine names
                on /etc/hosts on each machine i’ve added all the machines with names and the associated IP’s

                I don’t understand why the etcd cluster it’s down.
                Please advice.
                Thank You


                1. Leon’s avatar

                  Hi, similar problem with my setup as well. etcd-0 status is unhealthy due to certificate invalid for


                2. K@C’s avatar

                  Hi Adrian, Did you get a resolution to the error?
                  I am facing similar issue


                3. Rahul’s avatar

                  This is indisputably one of the best series i have found on kubernetes networking

                  Kudos to you sir


                4. Stig Thormodsrud’s avatar

                  Great article. The ansible playbook ran without error, but my nodes are NotReady:

                  ansible@invader2:~$ kubectl get componentstatus
                  scheduler Healthy ok
                  controller-manager Healthy ok
                  etcd-0 Healthy {“health”: “true”}

                  ansible@invader2:~$ kubectl get nodes
                  NAME STATUS AGE VERSION
                  sr2 NotReady 32m v1.7.0
                  sr3 NotReady 32m v1.7.0

                  On the nodes I see in syslog:

                  Feb 16 18:50:30 sr3 kubelet[2142]: W0216 18:50:30.294085 2142 cni.go:189] Unable to update cni config: No networks found in /etc/cni/net.d

                  Sure enough there is no /etc/cni directory. Any ideas what went wrong?



Your email address will not be published. Required fields are marked *