kubevirt/api-reference

API documentation

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

kubevirt/api-reference has 10+ forks on GitHub, is written in HTML, and was last pushed on Oct 17, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 42 minutes ago
Added to GitGenius on October 15th, 2026
Created on November 9th, 2017
Open Issues & Pull Requests: 0 (+0)
GitHub issues: Enabled
Number of forks: 14
Total Stargazers: 9 (+0)
Total Subscribers: 8 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 0
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

KubeVirt API Reference is an API documentation repository that provides generated reference material for the KubeVirt project.

The repository serves as the authoritative documentation source for developers working with KubeVirt's application programming interfaces. Its content is automatically generated from the OpenAPI specification maintained in the main KubeVirt project, ensuring that the documentation stays synchronized with the actual API implementation. This generation-based approach eliminates manual documentation drift and provides developers with accurate, up-to-date information about available endpoints, parameters, and response schemas.

Developers should use this reference when integrating with KubeVirt or building tools that interact with its APIs. It is essential for anyone implementing KubeVirt clients, operators, or extensions that need to understand the precise structure and behavior of the platform's interfaces. The documentation is particularly valuable for those new to KubeVirt who need to discover what capabilities are available and how to invoke them correctly.

The project maintains a straightforward relationship with its source: changes to the KubeVirt API specification automatically flow into updated documentation through the generation process. This tight coupling means the reference documentation reflects the current state of the project without requiring separate maintenance effort to keep specifications and documentation aligned.