[HEALTH]: Virtual Kubelet

[rochaporto]

Project name

Virtual Kubelet

Project Issue Link

virtual-kubelet/virtual-kubelet#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
• Move project to archived on landscape
• Remove maintainer list from 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)
• Archive project in LFX Insights (move to archive in PCC)
• Remove from CLOMonitor data

[rochaporto]

Following the discussion in the TOC public meeting on Oct 21st, we will try to:

• Organize a call with the TOC and the interested parties (virtual kubelet but also projects having it as a core dependency)
• Try to clarify the status and where the community is heading in this area

@rochaporto to coordinate this.

[pires]

Core but mostly inactive maintainer here. The project lives a precarious life but is stable. That said, I think it isn't and won't be in a better place any time soon as VK serves a microscopic niche, and maintaining it requires deep understanding of how the Kubernetes API machinery works and how that applies to Nodes.

IMO the project should be detached from CNCF but not archived so to allow it to live its course. I'm willing to take the ownership of the org, and eventually pass it on to someone else who's willing to maintain it.

[tskillian]

My team started a project about a year ago with a critical dependency on virtual kubelet. The project might not be very active, but as far as I know there aren't any critical issues/bugs that haven't been addressed. I don't think there's necessarily anything wrong with a project not needing updates very often (actually it can be a hint that the project is well-scoped), as long as there are people who can address any real issues when they come up.

How can me or someone from my team get more involved with managing the project? We've submitted some PRs and have been responding to people on slack and would be happy to take on more of a role if that'd be helpful