liquidmetal-dev / liquidmetal-dev/microvm-operator
improve replicaset scaling logic
Open
Nobody has claimed this yet.
kind/refactor
- Dominant language
- Go
- Stars
- 8
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
```
// TODO the way this works is very naive and often ends up deleting everything
// if the timing is wrong/right, find a better way
```
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 by locating the TODO for ReplicaSet scaling and tracing the current scaling flow. Determine the intended safe behavior when timing changes, then add coverage for scaling transitions. Done means the logic no longer risks deleting everything because of timing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100