{"id":3475,"date":"2015-08-12T23:35:01","date_gmt":"2015-08-13T05:35:01","guid":{"rendered":"http:\/\/benincosa.com\/?p=3475"},"modified":"2015-08-13T13:23:41","modified_gmt":"2015-08-13T19:23:41","slug":"kubernetes-on-metacloud-copc","status":"publish","type":"post","link":"https:\/\/benincosa.com\/?p=3475","title":{"rendered":"Kubernetes on Metacloud (COPC)"},"content":{"rendered":"

The Kubernetes 1.0 launch happened July 21st at OSCON<\/a> here in Portland, OR and I was super happy to be there in the back of the room picking up loads of free stickers while the big event happened. \u00a0I spent the day before at a Kubernetes bootcamp<\/a>, which was really just a lab on using it on GCE (or GKE for containers) and it was pretty cool. \u00a0But now I felt I really should do a little more to understand it.<\/p>\n

To install Kubernetes on Metacloud (or what Cisco now calls Cisco OpenStack Private Cloud<\/a>) I’m using CoreOS. \u00a0I like CoreOS because its lightweight and built for containers. \u00a0There are a few guides out there like the one on Digital Ocean that is pretty outdated (not even a year old!) that was good. \u00a0For installing Kubernetes on CoreOS on OpenStack its pretty easy now!<\/p>\n

I should note, that I’m using Cisco OpenStack Private Cloud, but these steps can be used with any OpenStack distribution. \u00a0I followed most of the documentation based on the Kubernetes documentation<\/a>. \u00a0(You’ll notice on there site that there is no instructions for OpenStack. \u00a0I opened an issue<\/a> of which I hope to help with).<\/p>\n

Anyway, the gist is here with all the instructions<\/a>, but I’m more of the mindset to use Ansible.<\/p>\n

Install Kubernetes<\/h3>\n

First download the cloud-init files that Kelsey Hightower created. \u00a0These make installing this super simple. \u00a0Get the master<\/a> and the node<\/a>.<\/p>\n

We then create a master task that looks something like this:<\/p>\n

  tasks: \r\n  - name: Deploy Kubernetes Master to Kube01\r\n    nova_compute:\r\n      state: present\r\n      auth_url: \"{{ lookup('env', 'OS_AUTH_URL') }}\"\r\n      login_username: \"{{ lookup('env', 'OS_USERNAME') }}\"\r\n      login_password: \"{{ lookup('env', 'OS_PASSWORD') }}\"\r\n      login_tenant_name: \"{{ project_name }}\"\r\n      name: \"{{ item }}\"\r\n      image_name: \"{{ coreos_image_name }}\"\r\n      key_name: \"{{ keypair }}\"\r\n      # 3 is m1.large\r\n      flavor_id: 3\r\n      meta: \r\n        group: Kube-Servers\r\n      security_groups: \"{{ security_group }}\"\r\n      user_data:  \"{{ lookup('file', 'files\/master.yaml') }}\"\r\n      floating_ip_pools:\r\n        - \"nova\"\r\n    with_items:\r\n      - kube01\r\n    register: nova<\/pre>\n
Here I’m heavily using environment variables that should be defined elsewhere. \u00a0I call them out with a vars_file that has most of these. \u00a0The credentials are stored in the ~\/.bash_profile and so live externally to the vars_file. \u00a0That’s where we keep our username, endpoints, and password.<\/p>\n
You’ll have to have a CoreOS image already created in your cloud to use this. \u00a0I got mine from here<\/a>. \u00a0Then I used glance and uploaded it.<\/p>\n
The user_data points to use the file that was created by the Kubernetes community and will configure upon boot the parameters required for Kubernetes.<\/p>\n
The minion nodes configuration is similar:<\/p>\n
- name: Deploy Kubernetes Minions\r\n    nova_compute:\r\n      state: present\r\n      auth_url: \"{{ lookup('env', 'OS_AUTH_URL') }}\"\r\n      login_username: \"{{ lookup('env', 'OS_USERNAME') }}\"\r\n      login_password: \"{{ lookup('env', 'OS_PASSWORD') }}\"\r\n      login_tenant_name: \"{{ project_name }}\"\r\n      name: \"{{ item }}\"\r\n      image_name: \"{{ coreos_image_name }}\"\r\n      key_name: \"{{ keypair }}\"\r\n      # 3 is m1.large\r\n      flavor_id: 3\r\n      meta: \r\n        group: Kube-Servers\r\n      security_groups: \"{{ security_group }}\"\r\n      user_data:  \"{{ lookup('file', 'files\/node.yaml') }}\"\r\n      floating_ip_pools:\r\n        - \"nova\"\r\n    with_items:\r\n      - kube02\r\n      - kube03\r\n      - kube04<\/pre>\n
Note that you have to edit the node.yml file to point to the master (kube01 in our example).<\/p>\n
At this point I’ve been a little lazy and didn’t go do the variable substitution. \u00a0Someday, I’ll get around to that. \u00a0But as a hint, since we registered ‘nova’ in the first task we can get the private IP address with this flag:<\/p>\n
- debug: var=nova.results[0].private_ip<\/pre>\n
Just put that after the creation of the master.<\/p>\n
The github repo for this is here<\/a>.<\/p>\n
Using Kubectl<\/h3>\n
Once our cluster is installed we can now run stuff. \u00a0I have a mac so I set it up like this following the instructions here<\/a>:<\/p>\n
cd \/usr\/local\/bin\/\r\nwget https:\/\/storage.googleapis.com\/kubernetes-release\/release\/v1.0.1\/bin\/darwin\/amd64\/kubectl --no-check-certificate\r\nchmod +x kubectl<\/pre>\n
Now we set the proxy up so we can run kubectl on our master:<\/p>\n
ssh -f -nNT -L 8080:127.0.0.1:8080 kube01<\/pre>\n
Make sure that when you check your path, kubectl from \/usr\/local\/bin shows up instead of maybe one from Google’s GCE stuff.<\/p>\n
Check that it works by running:<\/p>\n
kubectl version\r\nkubectl get nodes\r\nkubectl get pods\r\n\r\n<\/pre>\n
Now we can launch something! \u00a0Let’s use the Hello World example on the Kubernetes documentation site. \u00a0Create this file and name it hello-world.yaml<\/p>\n
apiVersion: v1\r\nkind: Pod\r\nmetadata:\r\n  name: hello-world\r\nspec:  # specification of the pod\u2019s contents\r\n  restartPolicy: Never\r\n  containers:\r\n  - name: hello\r\n    image: \"ubuntu:14.04\"\r\n    command: [\"\/bin\/echo\",\"hello\u201d,\u201dworld\"]<\/pre>\n
Then create it:<\/p>\n
kubectl create -f .\/hello-world.yaml<\/pre>\n
There are several other examples as well and I encourage you to go to the official guides<\/a>! \u00a0Let me know if this was helpful to you with a quick hello on Twitter<\/a>!<\/p>\n
 <\/p>\n","protected":false},"excerpt":{"rendered":"
The Kubernetes 1.0 launch happened July 21st at OSCON here in Portland, OR and I was super happy to be there in the back of the room picking up loads of free stickers while the big event happened. \u00a0I spent the day before at a Kubernetes bootcamp, which was really just a lab on using…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[1013,638,797,1001],"tags":[734,731,1011,798],"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/benincosa.com\/index.php?rest_route=\/wp\/v2\/posts\/3475"}],"collection":[{"href":"https:\/\/benincosa.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/benincosa.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/benincosa.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/benincosa.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=3475"}],"version-history":[{"count":4,"href":"https:\/\/benincosa.com\/index.php?rest_route=\/wp\/v2\/posts\/3475\/revisions"}],"predecessor-version":[{"id":3493,"href":"https:\/\/benincosa.com\/index.php?rest_route=\/wp\/v2\/posts\/3475\/revisions\/3493"}],"wp:attachment":[{"href":"https:\/\/benincosa.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=3475"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/benincosa.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=3475"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/benincosa.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=3475"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}