This project is mirrored from https://gitee.com/zyxjob/helm.git. Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
  1. 09 May, 2019 1 commit
  2. 02 May, 2019 1 commit
  3. 30 Apr, 2019 1 commit
  4. 24 Apr, 2019 1 commit
  5. 19 Apr, 2019 1 commit
  6. 18 Apr, 2019 2 commits
  7. 11 Apr, 2019 2 commits
  8. 10 Apr, 2019 2 commits
  9. 04 Apr, 2019 2 commits
  10. 30 Mar, 2019 1 commit
  11. 26 Mar, 2019 1 commit
  12. 25 Mar, 2019 1 commit
  13. 22 Mar, 2019 2 commits
    • Fernando Barbosa's avatar
      bf7106f6
    • Timofey Kirillov's avatar
      Fix `no RESOURCE with the name NAME found` · 5ffe4ce5
      Timofey Kirillov authored
      
      This is the fix for only one particular, but important case.
      
      The case when a new resource has been added to the chart and
      there is an error in the chart, which leads to release failure.
      In this case after first failed release upgrade new resource will be
      created in the cluster. On the next release upgrade there will be the error:
      `no RESOURCE with the name NAME found` for this newly created resource
      from the previous release upgrade.
      
      The root of this problem is in the side effect of the first release process,
      Release invariant says: if resouce exists in the kubernetes cluster, then
      it should exist in the release storage. But this invariant has been broken
      by helm itself -- because helm created new resources as side effect and not
      adopted them into release storage.
      
      To maintain release invariant for such case during release upgrade operation
      all newly *successfully* created resources will be deleted in the case
      of an error in the subsequent resources update.
      
      This behaviour will be enabled only when `--cleanup-on-fail` option used
      for `helm upgrade` or `helm rollback`.
      Signed-off-by: default avatarTimofey Kirillov <timofey.kirillov@flant.com>
      5ffe4ce5
  14. 18 Mar, 2019 1 commit
  15. 16 Mar, 2019 1 commit
  16. 09 Mar, 2019 1 commit
  17. 08 Mar, 2019 1 commit
  18. 04 Mar, 2019 2 commits
  19. 02 Mar, 2019 1 commit
  20. 26 Feb, 2019 1 commit
  21. 23 Feb, 2019 1 commit
  22. 19 Feb, 2019 1 commit
  23. 15 Feb, 2019 2 commits
  24. 12 Feb, 2019 3 commits
  25. 11 Feb, 2019 1 commit
  26. 10 Feb, 2019 1 commit
  27. 07 Feb, 2019 2 commits
  28. 06 Feb, 2019 1 commit
  29. 04 Feb, 2019 1 commit
  30. 01 Feb, 2019 1 commit