This project is mirrored from https://github.com/weaveworks/kured.git. Pull mirroring updated .
  1. 02 Apr, 2021 3 commits
  2. 29 Mar, 2021 8 commits
  3. 24 Mar, 2021 1 commit
    • Jean-Philippe Evrard's avatar
      Fix periodic jobs · 2a95f0b6
      Jean-Philippe Evrard authored
      Without this patch, the version of 1.20 is taken in jobs as 1.2.
      This is a problem, as it breaks all jobs, because there is no
      file to provision a cluster with kubernetes 1.2 (and we shouldn't
      do this!)
      
      This fixes it by ensuring there is no mangling of the version
      strings, and therefore the right file is used.
      2a95f0b6
  4. 22 Mar, 2021 2 commits
  5. 19 Mar, 2021 3 commits
  6. 11 Mar, 2021 3 commits
  7. 10 Mar, 2021 6 commits
  8. 09 Mar, 2021 4 commits
    • Daniel Holbach's avatar
      Merge pull request #296 from jackfrancis/node-annotations · 250b9bad
      Daniel Holbach authored
      add node annotations to identify kured reboot operations
      250b9bad
    • Daniel Holbach's avatar
      Merge pull request #294 from jackfrancis/always-drain · 32e01a84
      Daniel Holbach authored
      always drain before reboot
      32e01a84
    • Jack Francis's avatar
      add node annotations · baf83408
      Jack Francis authored
      adds a new --annotate-nodes daemonset runtime argument, which does the following when enabled:
      
      - adds a new node annotation "weave.works/kured-most-recent-reboot-needed" with a value of the current RFC3339 timestamp as soon as kured identifies that a node needs to be rebooted
      - adds a new node annotation "weave.works/kured-reboot-in-progress" with a value of the current RFC3339 timestamp as soon as kured identifies that a node needs to be rebooted
      - removes the annotation "weave.works/kured-reboot-in-progress" when kured has successfully rebooted the node
      baf83408
    • Jack Francis's avatar
      always drain before reboot · 93c8242b
      Jack Francis authored
      This changes the pre-reboot drain functionality so that it always runs, regardless of the value of the Unschedulable node property.
      
      Because kubectl drain is idempotent, we shouldn't have to worry about whether the node has already been set to Unschedulable (perhaps due to a prior, unsuccessful loop of the kured reboot cycle): we can run it over and over again. And because this drain func actually does a cordon + drain (and it only performs the drain if a cordon is successful), we can be sure that we aren't going to be thrashing this node w/ respect to scheduled pods.
      
      This also fixes an edge case: if the node has been marked Unschedulable out-of-band, but workloads remain Running on this node, kured will no longer reboot the node's underlying VM/machine while it is actively running pods.
      93c8242b
  9. 08 Mar, 2021 1 commit
  10. 02 Mar, 2021 2 commits
  11. 19 Feb, 2021 1 commit
  12. 18 Feb, 2021 1 commit
  13. 16 Feb, 2021 1 commit
  14. 11 Feb, 2021 1 commit
  15. 10 Feb, 2021 2 commits
  16. 08 Feb, 2021 1 commit