kubernetes-sigs
/
kubespray
mirror of https://github.com/kubernetes-sigs/kubespray.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Deploy a Production Ready Kubernetes Cluster
1,724 Commits
29 Branches
81 Tags
163 MiB
Jinja 90.7%
HCL 5.9%
Shell 1.6%
Python 1.5%
Dockerfile 0.1%
 
 
 
 
 
Go to file
Sergii Golovatiuk d8aa2d0a9e Change DNS policy for kubernetes components 
According to code apiserver, scheduler, controller-manager, proxy don't
use resolution of objects they created. It's not harmful to change
policy to have external resolver.

Signed-off-by: Sergii Golovatiuk <sgolovatiuk@mirantis.com>
 		2017-04-20 11:22:57 +02:00
.github GITHUB: Added issue template file 2017-01-03 16:09:35 +01:00
contrib Fixes for AWS Terraform Deployment and Updated Readme 2017-04-12 15:15:54 +02:00
docs Merge pull request #1232 from rsmitty/custom-flags 2017-04-17 14:01:32 -04:00
extra_playbooks Add minimal k8s upgrade playbook 2017-04-18 13:28:36 +03:00
inventory Fix for etcd variable issue 2017-04-12 12:59:49 +02:00
library Consolidating kube.py module 2017-01-27 11:28:11 -06:00
roles Change DNS policy for kubernetes components 2017-04-20 11:22:57 +02:00
scripts Allow collect-logs.yaml to operate without inventory vars 2017-04-10 18:49:17 +03:00
tests Wait for container creation in check network test 2017-04-04 13:12:24 +03:00
.gitignore Remove and ignore .bak files 2017-04-19 13:37:23 +02:00
.gitlab-ci.yml Add minimal k8s upgrade playbook 2017-04-18 13:28:36 +03:00
.gitmodules Remove submodules 2016-03-04 16:14:01 +01: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 upgrade etcd version from v3.0.6 to v3.0.17 2017-04-11 10:42:35 +08:00
RELEASE.md Clarify major/minor/maintainance releases 2017-01-12 11:25:04 +01:00
Vagrantfile Add support for atomic host 2017-03-01 09:38:19 -08:00
ansible.cfg Add timings to RECAP output. 2017-02-14 18:47:02 +01:00
cluster.yml Make any_errors_fatal configurable 2017-04-04 12:52:47 +03:00
code-of-conduct.md files needed to move kargo to k8s 2016-08-16 14:01:03 +02:00
requirements.txt pin ansible to version 2.2.1.0 2017-03-29 21:40:34 -04:00
reset.yml Add default var role 2017-02-23 12:07:17 +01:00
upgrade-cluster.yml Merge pull request #1153 from mattymo/graceful_drain 2017-04-04 17:33:53 +03:00
uploads.yml Upload files to a separate storage 2016-03-04 17:39:02 +01: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.17
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.