rancher/fleet

Deploy workloads from Git to large fleets of Kubernetes clusters

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 25 minutes ago
Added to GitGenius on April 7th, 2021
Created on March 8th, 2020
Open Issues & Pull Requests: 191 (+0)
Number of forks: 273
Total Stargazers: 1,724 (+0)
Total Subscribers: 74 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 7.9 days
Mean response time: 126.0 days
90th percentile: 371.0 days
Tracked items: 854

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 79% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "kind/regression" is answered fastest, typically in about an hour, while "area/documentation" waits about 8 weeks. 17% of tracked open issues have had no activity in three months. Only 3% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 116
New in 7 days: 9
Closed in 7 days: 2
Avg open age: 299 days
Stale 30+ days: 67
Stale 90+ days: 40

Recent activity

Opened in 7 days: 9
Closed in 7 days: 2
Comments in 7 days: 9
Events in 7 days: 44

Top labels

  • kind/bug (444)
  • kind/enhancement (207)
  • JIRA (175)
  • kind/chore (66)
  • area/performance (40)
  • kind/regression (27)
  • area/ui (22)
  • status/needs-triage (22)

Detailed Description

Fleet is a GitOps and HelmOps platform designed to deploy workloads from Git repositories to large fleets of Kubernetes clusters. Written in Go, the project addresses the operational challenges of managing multiple clusters at scale, whether that scale comes from the number of clusters themselves, the volume of deployments, or the complexity of multi-team organizations. While lightweight enough to function effectively on a single cluster, Fleet's architecture and feature set are optimized for scenarios involving substantial numbers of clusters or deployments.

The core functionality of Fleet centers on declarative deployment management. It can consume deployment specifications from multiple sources including raw Kubernetes YAML files, Helm charts, and Kustomize configurations, or any combination thereof. Regardless of the input format, Fleet normalizes all resources into Helm charts and uses Helm as the underlying deployment engine. This architectural choice provides consistency, auditability, and a high degree of control over what gets installed on each cluster. The platform emphasizes not just scalability but also visibility, giving operators clear insight into exactly what resources are deployed across their infrastructure.

The repository shows active development and maintenance patterns.

Fleet is classified across a comprehensive range of domains reflecting its multi-faceted role in the Kubernetes ecosystem: kubernetes, multi-cluster management, deployment automation, orchestration, infrastructure-as-code, continuous delivery, policy enforcement, GitOps, configuration management, and cloud native operations. These classifications underscore how the project bridges multiple operational concerns in modern infrastructure management.

The project maintains connections with other significant repositories in the Rancher ecosystem. Installation is straightforward, leveraging Helm for deployment and requiring users to add Git repositories as sources for deployment manifests. The project maintains comprehensive documentation at fleet.rancher.io and includes developer documentation in the repository itself, supporting both operators and contributors.