Fix runner pod to be cleaned up earlier regardless of the sync period #1299
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.
This is intended to be the minimum addition to the runner status to help the runner replicaset controller to notice that the runner pod is NotReady(due to whatever reasons like the runner container that is running an ephemeral runner completely successfully).
The runner replicaset controller is already able to terminate a NotReady runner and create a new runner as a replacement (if needed). That behavior, in combination with this fix, seems to fix the issue reported in #1291 for me.
Ref #1291