Skip to content
  1. Jan 13, 2017
  2. Jan 11, 2017
  3. Dec 28, 2016
  4. Dec 22, 2016
  5. Dec 13, 2016
  6. Dec 07, 2016
  7. Nov 29, 2016
  8. Nov 25, 2016
    • Bogdan Dobrelya's avatar
      Tune dnsmasq/kubedns limits, replicas, logging · 2d18e192
      Bogdan Dobrelya authored
      
      
      * Add dns_replicas, dns_memory/cpu_limit/requests vars for
      dns related apps.
      * When kube_log_level=4, log dnsmasq queries as well.
      * Add log level control for skydns (part of kubedns app).
      * Add limits/requests vars for dnsmasq (part of kubedns app) and
        dnsmasq daemon set.
      * Drop string defaults for kube_log_level as it is int and
        is defined in the global vars as well.
      * Add docs
      
      Signed-off-by: default avatarBogdan Dobrelya <bdobrelia@mirantis.com>
      2d18e192
  9. Nov 22, 2016
  10. Nov 21, 2016
  11. Nov 18, 2016
  12. Nov 10, 2016
  13. Nov 09, 2016
  14. Nov 04, 2016
  15. Oct 10, 2016
  16. Oct 04, 2016
  17. Aug 29, 2016
  18. Aug 24, 2016
  19. Aug 23, 2016
  20. 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
  21. Jul 22, 2016
  22. 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
  23. 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
  24. Jul 08, 2016
  25. May 22, 2016
    • Paul Czarkowski's avatar
      fixes issue #258 · c226b4e5
      Paul Czarkowski authored
      Kubernetes API server has an option:
      
      ```
      --advertise-address=<nil>: The IP address on which to advertise the apiserver to members of the cluster. This address must be reachable by the rest of the cluster. If blank, the --bind-address will be used. If --bind-address is unspecified, the host's default interface will be used.
      ```
      
      kargo does not set --bind-address, thus it binds to eth0, in vagrant and similar
      environments this causes issues because nodes cannot talk to eachother over eth0.
      
      This sets `--advertise-address` to `ip` if its set, otherwise the default behavior
      of is persisted by using `ansible_default_ipv4.address`.
      c226b4e5
  26. Apr 01, 2016
  27. Mar 31, 2016
  28. Mar 22, 2016
  29. Feb 01, 2016
  30. 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
  31. Dec 19, 2015
  32. Dec 16, 2015
  33. Dec 15, 2015
  34. Dec 14, 2015
Loading