Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • v2.28.0
  • v2.27.0
  • v2.25.1
  • v2.24.3
  • v2.26.0
  • v2.24.2
  • v2.25.0
  • v2.24.1
  • v2.22.2
  • v2.23.3
  • v2.24.0
  • v2.23.2
  • v2.23.1
  • v2.23.0
  • v2.22.1
  • v2.22.0
  • v2.21.0
  • v2.20.0
  • v2.19.1
  • v2.18.2
21 results

kubespray

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    Dan Bode authored
    Currently, the terraform script in contrib
    adds etcd role as a child of k8s-cluster in
    its generated inventory file.
    
    This is problematic when the etcd role is
    deployed on separate nodes from the k8s master
    and nodes. In this case, this leads to failures
    of the k8s node since the PKI certs required for
    that role have not been propogated.
    cb84b939
    History

    Kubespray Logo

    ##Deploy a production ready kubernetes cluster

    If you have questions, you can invite yourself to chat with us on Slack! SlackStatus

    • Can be deployed on AWS, GCE, 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 (deprecated, a newer go version soon)
    Ansible usual commands
    vagrant by simply running vagrant up (for tests purposes)

    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

    Build Status

    Google Compute Engine

              | Calico        | Flannel       | Weave         |

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

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