kube-rs/version-rs

Example kubernetes reflector and web server with axum

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

kube-rs/version-rs has 50+ stars on GitHub, is written in Rust, and was last pushed on Oct 14, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 54 minutes ago
Added to GitGenius on October 15th, 2026
Created on July 20th, 2019
Open Issues & Pull Requests: 3 (+0)
GitHub issues: Enabled
Number of forks: 8
Total Stargazers: 53 (+0)
Total Subscribers: 3 (+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

version-rs is an example Kubernetes reflector and web server built with Rust and axum.

The project demonstrates how to watch Kubernetes Deployments and expose their version information through a web API. It uses kube-rs's reflector and watcher stream abstractions to maintain a synchronized view of Deployments in a namespace, then serves this data via an axum web server on a `/versions` endpoint. The implementation is intentionally minimal, contained in under 100 lines of Rust code, making it suitable as a reference for developers learning these patterns.

This is a learning resource rather than a production tool. Developers should use it to understand how to build Kubernetes-aware applications in Rust, particularly those combining the kube-rs client library with axum for HTTP services. The project includes both local development against an existing cluster context and in-cluster deployment patterns, with support for local Docker builds on multiple architectures and Tilt-based development workflows.

The project maintains active continuous integration and publishes Docker images. Development activity shows regular updates to dependencies and build tooling, with examples kept current against upstream library changes.