argoproj / argoproj/argo-rollouts
Deprecating phase in rollout status
- Dominant language
- Go
- Stars
- 3.6k
- Forks
- 1.2k
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 28
Description
# Summary
What change needs making?
- Deprecating phase in the rollout status following the guidance of [k8s API convention](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#spec-and-status)
- infer the rollout status from its conditions
# Use Cases
When would you use this?
---
**Message from the maintainers**:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
Contributor guide
Research direction
Start by reading the Kubernetes API conventions guidance linked in the issue, then inspect the rollout status model and its conditions in the repository. Identify all uses of the phase field and the existing status calculation paths. Done means the phase is deprecated and rollout status is inferred from conditions without leaving affected users or callers inconsistent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100