[Docs] Add self node remediation as this is important for kubevirt
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 11
- Forks
- 76
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 26
Description
Please add self node remediation to the siderolabs docs as it is very useful for production (I dont know if talos has something like that built in when one node has no network connection that it reboots to release the rwo pvc volumes). When one use kubevirt and a node has not network then by default kubernetes does not release it and the vm would be down infinitely (until a manual person would come). the Self node remediation is solving that. So kubevirt works like vmware vsphere where a node failure or network downtime will automatically lead to the vm being started on a new node.
https://www.medik8s.io/remediation/self-node-remediation/how-it-works/
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 with the Sidero documentation structure and the linked Self Node Remediation explanation. Identify where KubeVirt production guidance belongs and document how remediation addresses node network loss and VM recovery. Done when the relevant docs clearly explain the setup and expected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 48/100