Skip to content
  1. 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
  2. Jul 22, 2016
  3. 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
  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. Jun 12, 2016
  6. May 28, 2016
    • Paul Czarkowski's avatar
      example env allow insecure-registry · 67147cf4
      Paul Czarkowski authored
      Many use cases of k8s involve running a local
      registry, chances are the person running this
      will learn the hard way that they need to allow
      insecure registry on the `kube_service_addresses`
      network.
      
      We should just default to settings this in
      `inventory/group_vars/all.yml` to help reduce
      potential friction for first time users.
      67147cf4
  7. May 25, 2016
  8. May 17, 2016
  9. May 11, 2016
  10. May 08, 2016
    • Paul Czarkowski's avatar
      Add native Vagrant support · 8f4e879c
      Paul Czarkowski authored
      This allows you to simply run `vagrant up` to get a 3 node HA cluster.
      
      * Creates a dynamic inventory and uses the inventory/group_vars/all.yml
      * commented lines in inventory.example so that ansible doesn't try to use it.
      * added requirements.txt to give easy way to install ansible/ipaddr
      * added gitignore files to stop attempts to save unwated files
      * changed `Check if kube-system exists` to `failed_when: false` instead of
      `ignore_errors`
      8f4e879c
  11. May 05, 2016
  12. May 04, 2016
  13. Mar 29, 2016
  14. Mar 23, 2016
  15. Mar 20, 2016
  16. Mar 07, 2016
  17. Feb 21, 2016
  18. Feb 10, 2016
  19. Feb 09, 2016
  20. 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
  21. Jan 22, 2016
  22. Jan 05, 2016
  23. Jan 04, 2016
  24. Dec 31, 2015
  25. Dec 24, 2015
  26. Dec 18, 2015
Loading