apache / apache/doris-operator
[Enhancement] when upgrading, the upgrading not finished, but the status will have available.
- Dominant language
- Go
- Stars
- 138
- Forks
- 72
- Avg merge
- 5d 12h
- Merged PRs (30d)
- 3
Description
### Search before asking
- [x] I had searched in the [issues](https://github.com/apache/doris-operator/issues?q=is%3Aissue) and found no similar issues.
### Description
when upgrading, FE(or BE) has 3 pods, the sequence 1 has finished, and the sequence 2 has not started. The status of ddc is available, so the status is not right.
This result is from the last code.
### Solution
_No response_
### Are you willing to submit PR?
- [x] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the upgrade status handling for FE and BE pods in the Go operator, focusing on how the DDC becomes available while a later pod sequence has not started. Reproduce the three-pod upgrade sequence and verify that availability is reported only after the full upgrade finishes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100