-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
oc status warning in case of automatic deployment rollbacks #8416
Comments
We should suggest |
We should also start emitting events when an automatic rollback happens but that's probably a separate issue. |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
/lifecycle frozen |
/sig master |
Having a deployment config running with its latest state being failed should be a warning in my opinion.
"dc/foo is running via an older deployment" and suggest to inspect the latest failure.
The text was updated successfully, but these errors were encountered: