oceanbase / oceanbase/ob-operator
[Enhancement]: Support to upgrade obagent
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 172
- Forks
- 44
- PR merge metrics
- No merged PRs in 30d
Description
Description
The current implementation only supports to add or delete obagent container, but sometimes it requires to upgrade obagent to fix certain bugs, it will be more convenient to directly update obagent container's version instead of delete it and add a new version again, this requires to recreate the observer pod 2 times.
Contributor guide
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 by tracing the operator's existing obagent add and delete handling and the observer pod recreation path. Done means an obagent version can be updated directly without deleting and re-adding it or recreating the observer pod twice.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100