liquidmetal-dev / liquidmetal-dev/microvm-operator
Ability to update microvms
Open
Nobody has claimed this yet.
kind/feature
- Dominant language
- Go
- Stars
- 8
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
I left this out of the replicaset for now but it would be useful to have.
Any microvm would be deleted anyway in the recreate, but it saves a command.
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 inspecting how the operator handles ReplicaSets and the recreate path for MicroVMs. Clarify which MicroVM changes should be applied in place and which require recreation, then verify that an update avoids unnecessary deletion and still leaves the desired MicroVM state applied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100