oc status warning in case of automatic deployment rollbacks
Open
Nobody has claimed this yet.
component/apps
component/cli
lifecycle/frozen
priority/P2
sig/master
- Dominant language
- Go
- Stars
- 8.7k
- Forks
- 4.8k
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 53
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the oc status command and trace how it reports deployment configurations after automatic rollbacks. Define the warning behavior for a configuration whose latest state failed while an older deployment is running, including a suggestion to inspect the latest failure; verify the result against relevant status scenarios.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- cli, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100