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,564 Commits
29 Branches
81 Tags
160 MiB
Jinja 89.4%
HCL 5.8%
Python 2.8%
Shell 1.7%
Dockerfile 0.1%
 
 
 
 
 
Go to file
Matthew Mosesohn 804e9a09c0 Migrate k8s data to etcd3 api store 
Default backend is now etcd3 (was etcd2).
The migration process consists of the following steps:
* check if migration is necessary
* stop etcd on first etcd server
* run migration script
* start etcd on first etcd server
* stop kube-apiserver until configuration is updated
* update kube-apiserver
* purge old etcdv2 data
 		2017-03-14 17:50:20 +03:00
.github GITHUB: Added issue template file 2017-01-03 16:09:35 +01:00
contrib Added Missing AWS IAM Profiles and Policies 2017-03-03 15:30:07 +01:00
docs Merge pull request #1113 from VincentS/AWS_IAM_PROFILES 2017-03-03 17:35:55 +03:00
inventory Added Support for OpenID Connect Authentication 2017-03-06 12:40:35 +01:00
library Consolidating kube.py module 2017-01-27 11:28:11 -06:00
roles Migrate k8s data to etcd3 api store 2017-03-14 17:50:20 +03:00
scripts remove temporary file 2017-02-15 17:40:05 +03:00
tests Change kube-api default port from 443 to 6443 2017-02-28 15:45:35 +01:00
.gitignore Updated gitignore pattern per review 2017-03-01 12:45:24 -08:00
.gitlab-ci.yml Add upgrade-cluster and reset playbooks to syntax check 2017-03-02 09:37:16 +04: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
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 Reference external documentation sources 2017-03-06 12:25:54 +01: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 Remove standalone etcd specific play, cleanup host mode 2017-03-04 00:34:26 +04:00
code-of-conduct.md files needed to move kargo to k8s 2016-08-16 14:01:03 +02:00
requirements.txt Update Ansible to 2.2.1 2017-01-19 13:46:46 +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

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
  • 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.