Exclude old pods in hco-catalogsource check after patch #299
Conversation
This file contains 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
An upgrade is initiated by patching the hco-catalogsource which causes its pod to redeploy. The wait for the catalog source pod to become ready should be on the new pod and not the old "Terminating" pod. Signed-off-by: Richard Su <rwsu@redhat.com>
rwsu
force-pushed
the
fix-catalogsource-wait-after-patch
branch
from
c3aee8d
to
180b04a
Compare
djzager
approved these changes
Sep 23, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
An upgrade is initiated by patching the hco-catalogsource which
causes its pod to redeploy. The wait for the catalog source pod
to become ready should be on the new pod and not the old
"Terminating" pod.