This project is mirrored from https://gitee.com/wangmingco/rook.git. Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
  1. 27 Mar, 2020 2 commits
  2. 26 Mar, 2020 11 commits
  3. 25 Mar, 2020 12 commits
  4. 24 Mar, 2020 6 commits
  5. 23 Mar, 2020 2 commits
    • Travis Nielsen's avatar
      Merge pull request #5072 from travisn/mon-affinity-duplicated-master · 4e4dc94c
      Travis Nielsen authored
      ceph: avoid duplication of mon anti-affinity
      4e4dc94c
    • Travis Nielsen's avatar
      ceph: avoid duplication of mon anti-affinity · a328f78a
      Travis Nielsen authored
      
      The default pod anti-affinity for the mons that rook adds
      automatically intended to be appended to any anti-affinity that
      is specified in the cluster CR.
      
      There is a bug in the ApplyToPodSpec() method that has long existed.
      The issue is that when antiaffinity is appended, it will append not only
      to the pod spec, but will modify the original placement spec. Thus, each
      mon that is started will have one more antiaffinity clause than the previous mon.
      
      This condition is rarely hit or noticed because it commonly is only hit
      in the canary pods. Since these pods are immediately deleted,
      there are no side effects of the duplicate affinity clauses. The place
      where it becomes an issue is when the mons are backed by a PVC. In this case,
      the mons do not have node affinity and will hit the code path that appends
      to the antiaffinity and thus modifies the original antiaffinity.
      Signed-off-by: default avatarTravis Nielsen <tnielsen@redhat.com>
      a328f78a
  6. 20 Mar, 2020 6 commits
  7. 19 Mar, 2020 1 commit