C12s/c12s-kubespray
3
0
Fork 0
Code Issues Pull requests Packages Projects Releases Wiki Activity
Deploy a Production Ready Kubernetes Cluster on bare metal or raw VMs - This is a clone of https://github.com/kubernetes-sigs/kubespray.git with a kitten twist.
1616 commits 17 branches 66 tags 141 MiB
Jinja 78.9%
HCL 10%
Python 5.7%
Shell 4.5%
Groovy 0.2%
Other 0.6%
Go to file
Matthew Mosesohn 3889c2e01c Add KVM hypervisor playbook to contrib 
Optional Ansible playbook for preparing a host for running Kargo.
This includes creation of a user account, some basic packages,
and sysctl values required to allow CNI networking on a libvirt network.
2017-03-21 19:50:01 +03:00
.github GITHUB: Added issue template file 2017-01-03 16:09:35 +01:00
contrib Add KVM hypervisor playbook to contrib 2017-03-21 19:50:01 +03:00
docs Fixed Formatting / Ansbile-Playbook Command 2017-03-16 17:53:48 +01:00
inventory Merge pull request #1155 from mattymo/helm 2017-03-20 17:00:06 +03:00
library Consolidating kube.py module 2017-01-27 11:28:11 -06:00
roles Merge pull request #1155 from mattymo/helm 2017-03-20 17:00:06 +03:00
scripts remove obsolete script 2017-03-17 20:09:36 +03:00
tests Add KVM hypervisor playbook to contrib 2017-03-21 19:50:01 +03:00
.gitignore Updated gitignore pattern per review 2017-03-01 12:45:24 -08:00
.gitlab-ci.yml Make reset check on idempotency check optional 2017-03-20 13:16:58 +03:00
.gitmodules Remove submodules 2016-03-04 16:14:01 +01:00
.travis.yml.bak Manual steps for Gitlab CI pipeline 2016-12-15 17:23:18 +01:00
ansible.cfg Add timings to RECAP output. 2017-02-14 18:47:02 +01:00
cluster.yml Move calico-policy-controller into separate role 2017-03-17 11:21:52 +01:00
code-of-conduct.md files needed to move kargo to k8s 2016-08-16 14:01:03 +02:00
CONTRIBUTING.md files needed to move kargo to k8s 2016-08-16 14:01:03 +02:00
LICENSE Create LICENSE 2016-03-01 15:37:01 +01:00
OWNERS Update OWNERS 2016-10-28 11:16:11 +04:00
README.md Added Jinja 2.8 to Docs 2017-03-15 13:11:09 +01:00
RELEASE.md Clarify major/minor/maintainance releases 2017-01-12 11:25:04 +01:00
requirements.txt limit jinja2 version to <2.9 2017-03-20 01:33:08 +03:00
reset.yml Add default var role 2017-02-23 12:07:17 +01:00
upgrade-cluster.yml Remove standalone etcd specific play, cleanup host mode 2017-03-04 00:34:26 +04:00
uploads.yml Upload files to a separate storage 2016-03-04 17:39:02 +01:00
Vagrantfile Add support for atomic host 2017-03-01 09:38:19 -08:00

README.md

Kubernetes Logo

##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 and inventory builder
vagrant by simply running vagrant up (for tests purposes)

Supported Linux distributions

  • Container Linux by CoreOS
  • Debian Jessie
  • Ubuntu 16.04
  • CentOS/RHEL 7

Note: Upstart/SysV init based OS types are not supported.

Versions of supported components

kubernetes v1.5.1
etcd v3.0.6
flanneld v0.6.2
calicoctl v0.23.0
canal (given calico/flannel versions)
weave v1.8.2
docker v1.12.5
rkt v1.21.0

Note: rkt support as docker alternative is limited to control plane (etcd and kubelet). Docker is still used for Kubernetes cluster workloads and network plugins' related OS services. Also note, only one of the supported network plugins can be deployed for a given single cluster.

Requirements

  • Ansible v2.2 (or newer) and python-netaddr is installed on the machine that will run Ansible commands
  • Jinja 2.8 (or newer) is required to run the Ansible Playbooks
  • The target servers must have access to the Internet in order to pull docker images.
  • The target servers are configured to allow IPv4 forwarding.
  • Your ssh key must be copied to all the servers part of your inventory.
  • 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.

Network plugins

You can choose between 4 network plugins. (default: calico)

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

  • calico: bgp (layer 3) networking.

  • canal: a composition of calico and flannel plugins.

  • 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. There is also an option to leverage built-in cloud provider networking instead. See also Network checker.

Community docs and resources

Tools and projects on top of Kargo

CI Tests

Gitlab Logo

Build graphs

CI/end-to-end tests sponsored by Google (GCE), DigitalOcean, teuto.net (openstack). See the test matrix for details.