Do not scale down deployment before resource deletion. Removing watch pod logic (seems to be also broken after 3.6 osio update) #6017
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.
What does this PR do?
Do not scale down deployment before resource deletion
deployment.scale(0, true);
hangs on osio after update to 3.6 version. Watching pods also seem to hang till timeout occurs.Changelog
(bugfix, update to support OpenShift 3.6+)
Release Notes
N / A
Docs PR
N / A