Kuadrant/kuadrant-operator

The Operator to install and manage the lifecycle of the Kuadrant components deployments.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 49 minutes ago
Added to GitGenius on January 24th, 2025
Created on December 6th, 2021
Open Issues & Pull Requests: 359 (+0)
Number of forks: 87
Total Stargazers: 90 (+0)
Total Subscribers: 10 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.7 days
Mean response time: 54.7 days
90th percentile: 154.8 days
Tracked items: 639

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 44% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "feat/extensions" is answered fastest, typically in about 15 hours, while "area/doc" waits about 5 weeks. 61% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 5% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 302
New in 7 days: 0
Closed in 7 days: 2
Avg open age: 270 days
Stale 30+ days: 274
Stale 90+ days: 241

Recent activity

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

Top labels

  • kind/enhancement (78)
  • feat/extensions (77)
  • kind/bug (59)
  • good first issue (36)
  • size/small (29)
  • kind/epic (25)
  • area/doc (24)
  • area/api (19)

Detailed Description

The Kuadrant Operator is a Kubernetes operator written in Go that manages the installation and lifecycle of Kuadrant components across containerized deployments. It extends gateway providers like Istio and Envoy Gateway by leveraging the Kubernetes Gateway API and Policy Attachment mechanisms to add enterprise-grade features including TLS, DNS, application authentication and authorization, and rate limiting capabilities.

The operator functions as a control plane component that enables policy-driven traffic management and security enforcement at the gateway layer. Rather than modifying gateway providers directly, Kuadrant uses a policy attachment pattern to inject additional functionality, allowing organizations to enhance their existing gateway infrastructure without replacing it. This architecture makes Kuadrant compatible with multiple gateway implementations, providing flexibility in how organizations deploy and manage their ingress and API gateway infrastructure.

The repository is classified across multiple infrastructure and cloud-native domains including container orchestration, Kubernetes, deployment automation, operator frameworks, and platform engineering. The codebase heavily emphasizes custom resource definitions and controller patterns typical of Kubernetes operators, enabling declarative management of Kuadrant policies and configurations through standard Kubernetes APIs.

The project is licensed under Apache 2.0, making it suitable for both open-source and commercial deployments. Documentation is comprehensive, with guides covering getting started, installation, and architectural design available through the official Kuadrant documentation site. The project actively encourages community participation through the Kubernetes Slack workspace, specifically the #kuadrant channel, where discussions about roadmap and development occur. Development contributions are supported through detailed guides explaining how to build the operator and test changes before submission, lowering barriers to entry for potential contributors.