interLink
/All repositories
Overview
HEALTH SCORE
Fair
56out of 100
Maintainer coverage drags the score down. Security posture and development cadence help keep it from falling further.
LIFECYCLE
Active
Consistent commits, responsive maintainers, regular releases, and healthy issue triage.
Health breakdown
Fair(56/100)
Maintainer availability, known risks and supply chain posture, and whether the project is actively developed or appropriately stable.
Maintainer responsiveness
Median response time is 1 day.
Bus factor
Only 3 active maintainers currently have merge rights.
Organization Diversity
Contributors come from 30 organizations only.
Project Achievements
Leaderboards
About
Virtual Kubelets are a powerful resource when it comes to exploit computing capacity managed outside of a Kubernetes cluster (possibly in a remote center). Although the current interface allows to create any number of custom implementations, it requires knowledge of the kubernetes internals.
interLink proposes a twofold model with clear roles and responsibilities. On the one hand a core component that interact through the Virtual Kubelet interface with the Kubernetes cluster, on the other hand a stateless plugin based architecture respecting the interLink OpenAPI specification. The latter is delegated to implement any pod execution details and interact with target resources. Plugins grant the flexibility and extensibility of the proposed system but most importantly they allow to hide the k8s interface complexity. Indeed, resource owners can build or customize plugins to define how a payload should be executed on their resources without any k8s knowledge.
First commit
Software value
$2.8M
Maturity
Sandbox
License(s)
Apache-2.0
MIT
Other
Links
Data sources
Git
GitHub