liquidmetal-dev / liquidmetal-dev/microvm-operator
Replacing one deployment host with another does not trigger a reconcile
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
start with:
```yaml
kind: MicrovmDeployment
spec:
hosts:
- name: host1
endpoint: 127.0.0.1:9090
```
create.
update to:
```yaml
kind: MicrovmDeployment
spec:
hosts:
- name: host2
endpoint: 127.0.0.1:9091
```
I should see the RS deleted from host1 and a new one created on host2. Right now nothing has noticed that this has changed
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 reproducing the update with the two MicrovmDeployment YAML manifests and trace the reconciliation path for changes under spec.hosts. Done means replacing host1 with host2 causes the existing RS to be deleted from host1 and a new RS to be created on host2.
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
- Clearly specified
- Newbie friendliness
- 45/100