Delete the pgdump pod once the backup has completed. #752
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cahoonpwork
added a commit
that referenced
this pull request
May 16, 2019
* fix pgo status not ready reporting, update dockerfiles to latest pgdg and backrest versions * Delete the pgdump pod once the backup has completed. (#752) * Delete the pgdump pod once the backup has completed. * Change pgdump cleanup to remove job instead of just pod once completed * fix primary delete in failover logic to wait for full deletion of pod * add crunchy yum repo to dockerfiles for scanning * Hlord update backport (#756) * Backporting yum update changes to 3.5.2 * Adding back the inclusion of crunchy pg11 repo * update pg version and operator version (#761) * Update pgBackRest version to 2.13 in rhel images (#764)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Type of Changes:
What is the current behavior? (link to any open issues here)
After a pdgump was executed, the pod would remain.
What is the new behavior (if this is a feature change)?
Once the pdgump is completed, the pod gets deleted
Other information:
[ch3617]