1. 05 Dec, 2018 1 commit
  2. 01 Jun, 2018 1 commit
  3. 25 May, 2018 1 commit
  4. 24 May, 2018 1 commit
  5. 15 May, 2018 1 commit
  6. 11 May, 2018 1 commit
  7. 13 Apr, 2018 1 commit
  8. 12 Apr, 2018 1 commit
  9. 10 Apr, 2018 2 commits
  10. 05 Apr, 2018 1 commit
  11. 03 Apr, 2018 1 commit
  12. 16 Mar, 2018 3 commits
  13. 15 Mar, 2018 1 commit
  14. 14 Mar, 2018 1 commit
  15. 13 Mar, 2018 3 commits
  16. 12 Mar, 2018 3 commits
  17. 07 Mar, 2018 1 commit
  18. 02 Mar, 2018 1 commit
  19. 28 Feb, 2018 5 commits
  20. 12 Feb, 2018 3 commits
  21. 11 Feb, 2018 2 commits
    • Yuxing's avatar
      Add Windows Agent crash-loop.ps1 script · 8311d813
      Yuxing authored
      Related issue https://github.com/rancher/rancher/issues/10662
      In order to support auto upgrade in Windows, add a new ps script for download and update binaries from rancher server.
      
      The crash-loop.ps1 script need to be set to be your failure action of your service.
      
      When we upgrading rancher server, we will need to stop Rancher server for a while.
      Then rancher-agent will stop because of it.
      And crash-loop.ps1 will be run and keep connectting to Rancher server, download the newest binaries into the host and start the service again.
      8311d813
    • Yuxing's avatar
      Refactor the Windows bootstrap agent logic · 2555a7af
      Yuxing authored
      1. Move most of the common logic into rancher-tools.psm1
      2. Fix the add host issue https://github.com/rancher/rancher/issues/11303
      3. No more download binaries in bootstrap agent. Download them when running the startup.ps1 script.
      2555a7af
  22. 01 Feb, 2018 3 commits
  23. 31 Jan, 2018 2 commits