Skip to content
  1. Jul 27, 2016
  2. Jul 26, 2016
    • Matthew Mosesohn's avatar
      Fix etcd standalone deployment · 1b1f5f22
      Matthew Mosesohn authored
      etcd facts are generated in kubernetes/preinstall, so etcd nodes need
      to be evaluated first before the rest of the deployment.
      
      Moved several directory facts from kubernetes/node to
      kubernetes/preinstall because they are not backward dependent.
      1b1f5f22
  3. Jul 20, 2016
  4. Jul 19, 2016
    • Bogdan Dobrelya's avatar
      Add etcd proxy support · 32cd6e99
      Bogdan Dobrelya authored
      
      
      * Enforce a etcd-proxy role to a k8s-cluster group members. This
      provides an HA layout for all of the k8s cluster internal clients.
      * Proxies to be run on each node in the group as a separate etcd
      instances with a readwrite proxy mode and listen the given endpoint,
      which is either the access_ip:2379 or the localhost:2379.
      * A notion for the 'kube_etcd_multiaccess' is: ignore endpoints and
      loadbalancers and use the etcd members IPs as a comma-separated
      list. Otherwise, clients shall use the local endpoint provided by a
      etcd-proxy instances on each etcd node. A Netwroking plugins always
      use that access mode.
      * Fix apiserver's etcd servers args to use the etcd_access_endpoint.
      * Fix networking plugins flannel/calico to use the etcd_endpoint.
      * Fix name env var for non masters to be set as well.
      * Fix etcd_client_url was not used anywhere and other etcd_* facts
      evaluation was duplicated in a few places.
      * Define proxy modes only in the env file, if not a master. Del
      an automatic proxy mode decisions for etcd nodes in init/unit scripts.
      * Use Wants= instead of Requires= as "This is the recommended way to
      hook start-up of one unit to the start-up of another unit"
      * Make apiserver/calico Wants= etcd-proxy to keep it always up
      
      Signed-off-by: default avatarBogdan Dobrelya <bdobrelia@mirantis.com>
      Co-authored-by: default avatarMatthew Mosesohn <mmosesohn@mirantis.com>
      32cd6e99
  5. Jul 15, 2016
  6. Jul 14, 2016
  7. Jul 07, 2016
  8. Jul 02, 2016
  9. Jun 28, 2016
  10. May 31, 2016
    • Evgeny L's avatar
      Scale-up functionality for etcd cluster · 0500f27d
      Evgeny L authored
      * Set ETCD_INITIAL_CLUSTER_STATE from `new` to `existing`,
      because parameter `new` makes sense only on cluster assembly
      stage.
      * If cluster exists and current node is not a part
      of the cluster, add it with command `etcdctl add member name url`.
      
      Closes kubespray/kargo/#270
      0500f27d
  11. May 23, 2016
  12. Apr 29, 2016
  13. Apr 25, 2016
  14. Feb 21, 2016
  15. Feb 15, 2016
  16. Feb 13, 2016
  17. Jan 31, 2016
  18. Jan 28, 2016
    • Greg Althaus's avatar
      Add variables and defaults for multiple types of ip addresses. · bedcca92
      Greg Althaus authored
      Each node can have 3 IPs.
      1. ansible_default_ip4 - whatever ansible things is the first IPv4 address
         usually with the default gw.
      2. ip - An address to use on the local node to bind listeners and do local
         communication.  For example, Vagrant boxes have a first address that is the
         NAT bridge and is common for all nodes.  The second address/interface should
         be used.
      3. access_ip - An address to use for node-to-node access.  This is assumed to
         be used by other nodes to access the node and may not be actually assigned
         on the node.  For example, AWS public ip that is not assigned to node.
      
      This updates the places addresses are used to use either ip or access_ip and walk
      up the list to find an address.
      bedcca92
  19. Jan 26, 2016
  20. Jan 25, 2016
  21. Jan 23, 2016
  22. Jan 22, 2016
  23. Jan 21, 2016
  24. Jan 15, 2016
  25. Dec 30, 2015
  26. Dec 29, 2015
  27. Dec 21, 2015
  28. Dec 18, 2015
  29. Dec 17, 2015
  30. Dec 15, 2015
  31. Dec 12, 2015
Loading