Skip to content
  1. May 08, 2019
  2. Apr 01, 2019
  3. Dec 25, 2018
  4. Dec 12, 2018
  5. Dec 11, 2018
  6. Jun 28, 2018
  7. Mar 17, 2018
  8. Jan 23, 2018
  9. Jun 16, 2017
  10. Jan 06, 2017
  11. Dec 23, 2016
  12. Dec 21, 2016
  13. Dec 19, 2016
  14. Dec 13, 2016
    • Bogdan Dobrelya's avatar
      Fix resolvconf · 0515814e
      Bogdan Dobrelya authored
      
      
      Do not repeat options and nameservers in the dhclient hooks.
      Do not prepend nameservers for dhclient but supersede and fail back
      to the upstream_dns_resolvers then default_resolver. Fixes order of
      nameservers placement, which is cluster DNS ip goes always first.
      
      Signed-off-by: default avatarBogdan Dobrelya <bdobrelia@mirantis.com>
      0515814e
  15. Dec 12, 2016
    • Bogdan Dobrelya's avatar
      Rework DNS stack to meet hostnet pods needs · 3117858d
      Bogdan Dobrelya authored
      * For Debian/RedHat OS families (with NetworkManager/dhclient/resolvconf
        optionally enabled) prepend /etc/resolv.conf with required nameservers,
        options, and supersede domain and search domains via the dhclient/resolvconf
        hooks.
      
      * Drop (z)nodnsupdate dhclient hook and re-implement it to complement the
        resolvconf -u command, which is distro/cloud provider specific.
        Update docs as well.
      
      * Enable network restart to apply and persist changes and simplify handlers
        to rely on network restart only. This fixes DNS resolve for hostnet K8s
        pods for Red Hat OS family. Skip network restart for canal/calico plugins,
        unless https://github.com/projectcalico/felix/issues/1185
      
       fixed.
      
      * Replace linefiles line plus with_items to block mode as it's faster.
      
      Signed-off-by: default avatarBogdan Dobrelya <bdobrelia@mirantis.com>
      Co-authored-by: default avatarMatthew Mosesohn <mmosesohn@mirantis.com>
      3117858d
  16. Dec 09, 2016
    • Bogdan Dobrelya's avatar
      Preconfigure DNS stack and docker early · a15d6267
      Bogdan Dobrelya authored
      
      
      In order to enable offline/intranet installation cases:
      * Move DNS/resolvconf configuration to preinstall role. Remove
        skip_dnsmasq_k8s var as not needed anymore.
      
      * Preconfigure DNS stack early, which may be the case when downloading
        artifacts from intranet repositories. Do not configure
        K8s DNS resolvers for hosts /etc/resolv.conf yet early (as they may be
        not existing).
      
      * Reconfigure K8s DNS resolvers for hosts only after kubedns/dnsmasq
        was set up and before K8s apps to be created.
      
      * Move docker install task to early stage as well and unbind it from the
        etcd role's specific install path. Fix external flannel dependency on
        docker role handlers. Also fix the docker restart handlers' steps
        ordering to match the expected sequence (the socket then the service).
      
      * Add default resolver fact, which is
        the cloud provider specific and remove hardcoded GCE resolver.
      
      * Reduce default ndots for hosts /etc/resolv.conf to 2. Multiple search
        domains combined with high ndots values lead to poor performance of
        DNS stack and make ansible workers to fail very often with the
        "Timeout (12s) waiting for privilege escalation prompt:" error.
      
      * Update docs.
      
      Signed-off-by: default avatarBogdan Dobrelya <bdobrelia@mirantis.com>
      a15d6267
  17. Sep 27, 2016
    • Bogdan Dobrelya's avatar
      Allow subdomains of dns_domain and fix kubelet restarts · 5fd43b7c
      Bogdan Dobrelya authored
      
      
      * Add a var for ndots (default 5) and put it hosts' /etc/resolv.conf.
      * Poke kube dns container image to v1.7
      * In order to apply changes to kubelet, notify it to
      be restarted on changes made to /etc/resolv.conf. Ignore errors as the kubelet
      may yet to be present up to the moment of the notification being processed.
      * Remove unnecessary kubelet restart for master role as the node role ensures
      it is up and running. Notify master static pods waiters for apiserver,
      scheduler, controller-manager instead.
      
      Signed-off-by: default avatarBogdan Dobrelya <bdobrelia@mirantis.com>
      5fd43b7c
  18. Sep 26, 2016
  19. Sep 23, 2016
Loading