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
I've noticed that if you update the ISBService, the Pipeline will momentarily indicate that it's "Failed". I'm concerned about this potential scenario:
User updates both isbsvc and pipeline in github
ArgoCD uses sync waves such that it will update isbsvc first
isbsvc is updated, which pauses pipelines
isbsvc is done, so pipelines are allowed to run
pipeline is temporarily marked "Failed" because "isbsvc is unhealthy"
Numaplane updates the Pipeline spec without pausing because the pipeline is technically "Failed"
Therefore, we should have a delay after which if it's still failed, we can just do the reapply.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered:
Describe the bug
I've noticed that if you update the ISBService, the Pipeline will momentarily indicate that it's "Failed". I'm concerned about this potential scenario:
Therefore, we should have a delay after which if it's still failed, we can just do the reapply.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: