Uploaded image for project: 'must-gather'
  1. must-gather
  2. MG-56

Avoid immediate deletion of must-gather job/CR

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Product / Portfolio Work
    • 5
    • False
    • Hide

      None

      Show
      None
    • False
    • 3
    • OAPE Sprint 275, OAPE Sprint 276
    • 2

      Currently must-gather jobs/CRs are deleted as soon as it completes (in both cases success or failure). User is not able to get the update about the must-gather operation as status updates on jobs/CRs are lost because of deletion. Make this undeletion behavior flag driven.

      Avoid deletion of these CRs.

      Explore and decide an appropriate plan for life-time of these jobs/CRs. 

      Acceptance criteria:

      1. The undeletion behavior should be flag driven - retainResourcesOnCompletion
      2. CRs should not get deleted irrespective of the retainResourcesOnCompletion flag value{}
      3. Must-gather jobs/secrets should not get deleted after the operation completes if the retainResourcesOnCompletion flag is set to true.
      4. Must-gather jobs/secrets should get deleted after the operation completes if the retainResourcesOnCompletion flag is unset or set to false.
      5. The pods associated with jobs will get deleted on job success/failure(after retries) irrespective of the retainResourcesOnCompletion flag value as this is being controlled by job controller

       

              rh-ee-rausingh Raushan Kumar Singh
              rh-ee-smuley Shivprakash Muley
              Keenon Lee Keenon Lee
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: