Skip to content
Snippets Groups Projects
  1. Nov 08, 2016
  2. Oct 21, 2016
  3. Oct 15, 2016
  4. Oct 05, 2016
  5. Sep 18, 2016
  6. Sep 15, 2016
  7. Sep 14, 2016
  8. Sep 13, 2016
  9. Aug 26, 2016
  10. Aug 23, 2016
  11. Aug 08, 2016
  12. 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
  13. Jul 25, 2016
    • Bogdan Dobrelya's avatar
      Add HA/LB endpoints for kube-apiserver · 731d32af
      Bogdan Dobrelya authored
      
      * Add HA docs for API server.
      * Add auto-evaluated internal endpoints and clarify the loadbalancer_apiserver
      vars and usecases.
      * Use facts for kube_apiserver to not repeat code and enable LB endpoints use.
      * Use /healthz check for the wait-for apiserver.
      * Use the single endpoint for kubelet instead of the list of apiservers
      * Specify kube_apiserver_count to for HA layout
      
      Signed-off-by: default avatarBogdan Dobrelya <bdobrelia@mirantis.com>
      731d32af
  14. Jul 22, 2016
  15. Jul 21, 2016
    • Bogdan Dobrelya's avatar
      Add HA/LB endpoints for kube-apiserver · a70c3b66
      Bogdan Dobrelya authored
      
      * Add auto-evaluated internal endpoints and clarify the loadbalancer_apiserver
      vars and usecases.
      * Add loadbalancer_apiserver_localhost (default false). If enabled, override
      the external LB and expect localhost:443/8080 to be new internal only frontends.
      * Add kube_apiserver_multiaccess to ignore loadbalancers, and make clients
      to access the apiservers as a comma-separated list of access_ip/ip/ansible ip
      (a default mode). When disabled, allow clients to use the given loadbalancers.
      * Define connections security mode for kube controllers, schedulers, proxies.
      It is insecure be default, which is the current deployment choice.
      * Rework the groups['kube-master'][0] hardcode defining the apiserver
      endpoints.
      * Improve grouping of vars and add facts for kube_apiserver.
      * Define kube_apiserver_insecure_bind_address as a fact, add more
      facts for ease of use.
      
      Signed-off-by: default avatarBogdan Dobrelya <bdobrelia@mirantis.com>
      a70c3b66
  16. Jul 20, 2016
  17. Jun 12, 2016
  18. Jun 11, 2016
  19. Apr 20, 2016
  20. Apr 13, 2016
  21. Apr 12, 2016
  22. Apr 11, 2016
  23. Mar 30, 2016
  24. Mar 29, 2016
  25. Mar 23, 2016
  26. Feb 23, 2016
  27. Feb 21, 2016
  28. Feb 18, 2016
  29. Feb 13, 2016
  30. Feb 09, 2016
  31. Feb 01, 2016
  32. 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
  33. Jan 25, 2016
Loading