https://github.com/gambol99/ansible-kubernetes

A collection of plays for configuration of Kubernetes on CoreOS
https://github.com/gambol99/ansible-kubernetes

Last synced: 11 days ago
JSON representation

A collection of plays for configuration of Kubernetes on CoreOS

• Host: GitHub
• URL: https://github.com/gambol99/ansible-kubernetes
• Owner: gambol99
• Created: 2015-05-27T11:25:45.000Z (over 9 years ago)
• Default Branch: master
• Last Pushed: 2016-10-25T22:19:38.000Z (about 8 years ago)
• Last Synced: 2024-04-17T15:10:30.204Z (9 months ago)
• Language: Python
• Homepage:
• Size: 1.17 MB
• Stars: 9
• Watchers: 3
• Forks: 2
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
## **CoreOS Kubernetes**

The respository holds a ansible installation for deployment of below on CoreOS

  - kubernetes framework

  - ceph storage layer

  - glusterfs storage

Note: all the services are actually deployed via fleet, through the unit files are first templated and customized per role and or location. 

#### **Ansible**

A small container is deployed via fleet during the cloudinit process allowing us to run ansible on the boxes. We then map into various areas of the host filesystem so we may drop files, configs, certs etc etc.

#### **Sites**

----

The location / sites data (found in /sites//vars/.yml) is the datacenter / region specific information - username, password, networks, dns, provider details is region specific; The design being your playbooks and roles are abstract with the location data permitting the same code to be reused across multiple environments, providers and regions. Note, these are passed into the play via -e location=

#### **Bastion hosts**

----

Dropped into the base directory is a ssh.config which is used to configure the bastion setup; all command and plays being run by Ansible are routed by bastion host. For the dev and vagrant i'm just reusing a actual box to act as bastion as I can't be asked to waste the memory a separate host.

#### **Dynamic Inventory**

-----

Dynamic inventory for vagrant and vcloud has been written and inventory directory. Both of these along with EC2 the inventory/group.yml to perform the groups and groups of groups and keeps things simple.

##### **Groups**

Inside the inventory/ directory is a group.yml which is used to place the hosts into ansible groups, it effectively does nothing more than using regexes and hostnames and placing them into the appointed group.  

#### **Building in vagrant**

----

    # for a kubernetes deployment

    [jest@starfury ansible-kubernetes]$ make sbx

    # the sbx-play with run the ansible playbook again

    [jest@starfury ansible-kubernetes]$ make sbx-play

    # build the ceph storage layer

    [jest@starfury ansible-kubernetes]$ make ceph

Take a look at the Makefile to see whats happening.

#### **Etcd Discovery**

Assuming your using CoreOS a discovery token will automatially genereated for you under the var/location/sbx.discovery.yml on the first vagrant up.