Skip to content
  1. Sep 02, 2018
    • Pablo Estigarribia's avatar
      ensure there is pin priority for docker package to avoid upgrade of docker to incompatible version · 7cbe3c21
      Pablo Estigarribia authored
      ensure there is pin priority for docker package to avoid upgrade of docker to incompatible version
      
      remove empty when line
      
      ensure there is pin priority for docker package to avoid upgrade of docker to incompatible version
      
      force kubeadm upgrade due to failure without --force flag
      
      ensure there is pin priority for docker package to avoid upgrade of docker to incompatible version
      
      added nodeSelector to have compatibility with hybrid cluster with win nodes, also fix for download with missing container type
      
      fixes in syntax and LF for newline in files
      
      fix on yamllint check
      
      ensure there is pin priority for docker package to avoid upgrade of docker to incompatible version
      
      some cleanup for innecesary lines
      
      remove conditions for nodeselector
      7cbe3c21
  2. Aug 24, 2018
  3. Aug 23, 2018
  4. Aug 17, 2018
  5. Jul 11, 2018
  6. Jul 06, 2018
  7. Jun 30, 2018
  8. Jun 24, 2018
  9. Jun 22, 2018
  10. Jun 18, 2018
  11. Jun 06, 2018
  12. May 30, 2018
  13. May 11, 2018
    • Matthew Mosesohn's avatar
      refactor vault role (#2733) · 07cc9819
      Matthew Mosesohn authored
      * Move front-proxy-client certs back to kube mount
      
      We want the same CA for all k8s certs
      
      * Refactor vault to use a third party module
      
      The module adds idempotency and reduces some of the repetitive
      logic in the vault role
      
      Requires ansible-modules-hashivault on ansible node and hvac
      on the vault hosts themselves
      
      Add upgrade test scenario
      Remove bootstrap-os tags from tasks
      
      * fix upgrade issues
      
      * improve unseal logic
      
      * specify ca and fix etcd check
      
      * Fix initialization check
      
      bump machine size
      07cc9819
  14. May 02, 2018
  15. May 01, 2018
  16. Apr 26, 2018
  17. Apr 23, 2018
  18. Apr 18, 2018
  19. Apr 11, 2018
  20. Apr 01, 2018
    • woopstar's avatar
      Etcd cluster setup makeover · 86e3506a
      woopstar authored
      The current way to setup the etc cluster is messy and buggy.
      
      - It checks for cluster is healthy before the cluster is even created.
      - The unit files are started on handlers, not in the task, so you mess with "flush handlers".
      - The join_member.yml is not used.
      - etcd events cluster is not configured for kubeadm
      - remove duplicate runs between running the role on etcd nodes and k8s nodes
      86e3506a
  21. Mar 31, 2018
  22. Mar 30, 2018
  23. Mar 28, 2018
  24. Mar 26, 2018
  25. Mar 14, 2018
  26. Mar 06, 2018
  27. Mar 01, 2018
  28. Feb 22, 2018
  29. Feb 21, 2018
  30. Feb 12, 2018
  31. Feb 09, 2018
    • Damian Nowak's avatar
      Enable OOM killing · f8a59446
      Damian Nowak authored
      When etcd exceeds its memory limit, it becomes useless but keeps running.
      We should let OOM killer kill etcd process in the container, so systemd can spot
      the problem and restart etcd according to "Restart" setting in etcd.service unit file.
      If OOME problem keep repeating, i.e. it happens every single restart,
      systemd will eventually back off and stop restarting it anyway.
      
      --restart=on-failure:5 in this file has no effect because memory allocation error
      doesn't by itself cause the process to die
      
      Related: https://github.com/kubernetes-incubator/kubespray/blob/master/roles/etcd/templates/etcd-docker.service.j2
      
      This kind of reverts a change introduced in #1860.
      f8a59446
  32. Jan 30, 2018
  33. Jan 29, 2018
  34. Jan 09, 2018
Loading