vitobotta/hetzner-k3s

The easiest and fastest way to create production-ready Kubernetes clusters on Hetzner Cloud

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 hour ago
Added to GitGenius on September 18th, 2026
Created on August 7th, 2021
Open Issues & Pull Requests: 35 (+0)
GitHub issues: Enabled
Number of forks: 233
Total Stargazers: 3,682 (+0)
Total Subscribers: 34 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.9 hours
Mean response time: 8.1 days
90th percentile: 11.9 days
Tracked items: 145

Most active contributors

Sign in to see contributor activity.

How this project is maintained

Roughly one issue in three opened in the past year never receives a reply. 100% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. 71% of issues opened in the past year have been closed, leaving a working backlog.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 25
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 240 days
Stale 30+ days: 23
Stale 90+ days: 20

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

Detailed Description

hetzner-k3s is a CLI tool that creates production-ready Kubernetes clusters on Hetzner Cloud in minutes without requiring Terraform, a management cluster, or third-party credential access.

The tool solves the problem of slow and complex Kubernetes cluster provisioning by automating the entire setup process through a single command-line interface. It works by taking a human-readable YAML configuration file and orchestrating the creation of infrastructure on Hetzner Cloud, automatically installing essential components including the Cloud Controller Manager, CSI driver, System Upgrade Controller, and Cluster Autoscaler. The approach eliminates the need to learn multiple infrastructure-as-code tools or maintain separate provisioning pipelines.

Teams should choose this tool if they want to run Kubernetes on Hetzner Cloud without the operational overhead of managing Terraform configurations or maintaining a separate management cluster. It suits projects of any scale, from small three-node high-availability clusters to large deployments, and is particularly valuable for teams that prioritize simplicity and cost efficiency. The tool keeps your Hetzner API token local to your machine rather than sharing credentials with third-party services, giving you complete control over your infrastructure with no recurring platform fees beyond Hetzner's infrastructure costs.

The project shows consistent maintenance with regular commits and active engagement with issues and pull requests. The maintainer actively solicits community contributions and maintains open communication channels through GitHub discussions. Development activity indicates ongoing refinement of the tool's core functionality and responsiveness to user feedback.