[HEALTH]: Virtual Kubelet
- Dominant language
- HTML
- Stars
- 1.9k
- Forks
- 724
- Avg merge
- 6d 12h
- Merged PRs (30d)
- 4
Description
### Project name
Virtual Kubelet
### Project Issue Link
https://github.com/virtual-kubelet/virtual-kubelet/issues/1347
### Concern
The virtual kubelet project remains a core dependency to end user deployments looking to scale out their deployments, as well as to new projects (supernetes, interLink, ...) targeting the bridge between multiple clusters or between cloud native and non cloud native deployments (such as HPC).
The project does not seem to have a very active community:
* One issue closed during 2025
* Little activity in contributions and issue interaction
Some of the functionality appearing in these new projects seem to add functionality that could be better consolidated in the virtual kubelet itself. The goal is not to trigger a project archival review, but to get the TOC to help consolidating the efforts around it.
### Prior engagement
Not yet.
### Additional Information
_No response_
### Archiving Checklist (If project is determined for archival)
**NOTE:** Only applicable if the project opts to self-archive, or is initiated as a last possible option following a TOC vote.
To proceed with the archival checklist, add the `level/archive` label and assign: caniszczyk, mrbobbytables, idvoretskyi, jeefy, castrojo, krook
### Archiving Checklist
- [ ] TOC vote to archive passed
- [ ] Move project (logo) to archived in the [artwork repo](https://github.com/cncf/artwork)
- [ ] Move project to archived on [landscape](https://github.com/cncf/landscape)
- [ ] Remove maintainer list from [project-maintainers.csv](https://github.com/cncf/foundation/blob/main/project-maintainers.csv)
- [ ] Remove from staff list of maintainer emails
- [ ] Archive (lock) maintainers mailing list (groups.io)
- [ ] Remove ML from maintainers@ mailing group (google groups)
- [ ] Remove project (logo) from all slide decks (contact pr@cncf.io)
- [ ] Remove project (logo) from event sites (contact events@cncf.io)
- [ ] Notify DevEx team to remove from event Maintainer Project Opportunities
- [ ] Remove from maintainers & project from service desk
- [ ] Remove from CNCF store (reach out to staff or email store@cncf.io)
- [ ] Archive DevStats data (open issue in [devstats repo](https://github.com/cncf/devstats/issues))
- [ ] Archive project in LFX Insights (move to archive in PCC)
- [ ] Remove from [CLOMonitor data](https://raw.githubusercontent.com/cncf/clomonitor/main/data/cncf.yaml)
Contributor guide
Assessment
This issue has not been assessed yet.