##Deploy a production ready kubernetes cluster

If you have questions, join us on the kubernetes slack, channel #kargo.

• Can be deployed on AWS, GCE, Azure, OpenStack or Baremetal
• High available cluster
• Composable (Choice of the network plugin for instance)
• Support most popular Linux distributions
• Continuous integration tests

To deploy the cluster you can use :

kargo-cli
Ansible usual commands
vagrant by simply running vagrant up (for tests purposes)

• Requirements
• Getting started
• Vagrant install
• CoreOS bootstrap
• Ansible variables
• Cloud providers
• OpenStack
• AWS
• Azure
• Network plugins
• Roadmap

Kargo vs Kops

Kargo runs on bare metal and most clouds, using Ansible as its substrate for provisioning and orchestration. Kops performs the provisioning and orchestration itself, and as such is less flexible in deployment platforms. For people with familiarity with Ansible, existing Ansible deployments or the desire to run a Kubernetes cluster across multiple platforms, Kargo is a good choice. Kops, however, iss more tightly integrated with the unique features of the clouds it supports so it could be a better choice if you know that you will only be using one platform for the foreseeable future.

Supported Linux distributions

• CoreOS
• Debian Wheezy, Jessie
• Ubuntu 14.10, 15.04, 15.10, 16.04
• Fedora 23
• CentOS/RHEL 7

Versions

kubernetes v1.4.6
etcd v3.0.6
flanneld v0.6.2
calicoctl v0.22.0
weave v1.6.1
docker v1.10.3

Requirements

• The target servers must have access to the Internet in order to pull docker images.
• The firewalls are not managed, you'll need to implement your own rules the way you used to. in order to avoid any issue during deployment you should disable your firewall
• Copy your ssh keys to all the servers part of your inventory.
• Ansible v2.x and python-netaddr

Network plugins

You can choose between 3 network plugins. (default: flannel with vxlan backend)

• flannel: gre/vxlan (layer 2) networking.

• calico: bgp (layer 3) networking.

• weave: Weave is a lightweight container overlay network that doesn't require an external K/V database cluster.
  (Please refer to weave troubleshooting documentation)

The choice is defined with the variable kube_network_plugin

CI Tests

Google Compute Engine

          | Calico        | Flannel       | Weave         |

------------- | ------------- | ------------- | ------------- | Ubuntu Xenial |||| CentOS 7 |||| CoreOS (stable) ||||

CI tests sponsored by Google (GCE), and teuto.net for OpenStack.