You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here we only check if the status of a delete pipeline has succeeded, and requeue if it hasn't. This means that if a pipeline fails, it's infinitely requeued (with a fastRequeue):
Here we only check if the status of a delete pipeline has succeeded, and requeue if it hasn't. This means that if a pipeline fails, it's infinitely requeued (with a
fastRequeue
):This may become an issue if many pipelines fail at once on the same cluster: the continual requeuing may end up using a chunk of the resources.
It's unclear what the right behaviour is here (since returning an error will also requeue), so this ticket is a placeholder/RFC!
The text was updated successfully, but these errors were encountered: