planetscale / planetscale/vitess-operator
Storage Update Strategy
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 372
- Forks
- 102
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 15
Description
Hello!
I think that something needs to be re-jigged here, it looks like if you have your update strategy set to external, you can change storage to be immediate
but we have a requirement for the opposite, we have immediate, and want ONLY storage to be handled externally.
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 with pkg/controller/vitessshard/reconcile_disk.go at line 27 and trace how the external and immediate update strategies affect storage changes. Confirm the desired behavior for an immediate strategy with externally managed storage, then identify the relevant reconciliation path and tests, if present. Done means the two storage-management choices can be configured independently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100