Kite 🪁

🚧 Proof of Concept - APIs and core functionality may change. See Status below.

---

What is Kite?

Kite is a set of components that detect, create and track issues that can disrupt applications in your cluster.

Typical issues include:

• Tekton PipelineRun failures
• Release pipeline errors
• MintMaker issues
• Cluster-wide problems affecting builds/releases

---

Why Kite?

• Single source of truth for diagnosing cluster incidents
• Extensible controllers to watch your own resources
• Automation-first via webhooks and API
• CLI-first tooling for developers, SREs and power users

---

Features

• Issue Tracking: Centralized, extensible store for build/test failures, release problems, and more.
• CLI Integration: Use a standalone CLI tool to query issues in the store.
• Namespace Scoping: Issues are namespaces for isolation and security. (WIP)
• Automation: Webhooks for automatic issue creation/resolution.
• REST API: Integrate with external tools (such as the Issues Dashboard WIP).
• Extensible Operator: Add custom controllers to watch cluster resources and open/resolve issues in Kite.

All these components work together to create and track issues that may disrupt your ability to build and deploy applications in your cluster.

---

Repository structure

• Backend: packages/backend: Go server (Gin) + PostgreSQL database.

• CLI: packages/cli: Go CLI tool (can also run as a kubectl plugin.)

• Operator: packages/operator: Kubernetes operator for resource watchers.

Included controller(s):

• PipelineRun Controller: Tracks Tekton PipelineRun successes/failures (reference controller implementation)

---

Getting started

Integrate with Kite (recommended path)

1. Build a custom controller that watches your resources and posts state changes
2. Implement a custom webhook endpoint with payloads tailored to your events. You can also use the standard API, but webhooks usually make issue creation/resolution simpler.

Alternative approach

See the External Service Integration docs.

---

Docs

• API
• Webhooks
• Controller Development Guide
• External Service Integration

---

Prerequisites

To work with this project, ensure you have the following installed:

• Docker or Podman
• Go v1.23 or later
• Make
• Minikube – for local development
• kubectl – for local development

---

Status

This is still a proof-of-concept project. See the Roadmap below for a high-level progress overview and plans.

Roadmap

• Backend API service is built and released through Konflux
• Backend API service is running on a public staging cluster
• Current - Bridge Operator is built and released through Konflux
• Bridge Operator is live on a public staging cluster
• Konflux teams onboard their controllers onto Bridge Operator, generating issues