perses/perses-operator

Perses Operator - Manage Perses on Kubernetes - Deploy dashboard as CR

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

perses/perses-operator has 50+ stars and 20+ forks on GitHub, is written in Go, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 48 minutes ago
Added to GitGenius on October 15th, 2026
Created on August 28th, 2023
Open Issues & Pull Requests: 32 (+0)
GitHub issues: Enabled
Number of forks: 24
Total Stargazers: 51 (+0)
Total Subscribers: 1 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.1 hours
Mean response time: 31.0 days
90th percentile: 85.3 days
Tracked items: 86

Maintainer activity

6 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 7% of issues opened in the past year have never received a reply. 71% of issues opened in the past year have been closed, leaving a working backlog. Three people close 91% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 18
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 216 days
Stale 30+ days: 17
Stale 90+ days: 11

Recent activity

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

Top labels

  • kind/feature (32)
  • priority/P0 (19)
  • ci/cd (12)
  • kind/bug (11)
  • needs-triage (9)
  • priority/P1 (9)
  • github_actions (8)
  • priority/P2 (6)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Perses Operator is a Kubernetes operator that manages Perses observability dashboards and related resources on Kubernetes clusters.

The operator solves the problem of deploying and managing Perses instances and their associated dashboards and datasources in Kubernetes environments. It works by extending Kubernetes with custom resource definitions that represent Perses servers, dashboards, datasources, and global datasources. When you declare these resources in Kubernetes, the operator watches the API server for changes and automatically reconciles the actual state of your Perses deployments to match your desired configuration. This enables dashboard-as-code workflows where dashboards and datasources are managed declaratively alongside other infrastructure.

The tool suits teams running Perses on Kubernetes who want to manage dashboards and datasources through Kubernetes manifests rather than manual API calls. It is particularly valuable for multi-instance deployments where you need to sync dashboards across multiple Perses servers, since it supports instance selectors and namespace-to-project mapping for isolation. The operator handles storage flexibility by supporting both SQL databases and file-based storage with persistent volumes or ephemeral storage. It also provides native support for TLS, mTLS, and multiple authentication methods including BasicAuth, OAuth, and Kubernetes-native authentication. Built-in Prometheus metrics and alerting rules make it compatible with Prometheus Operator for monitoring the operator itself.

The project is under active development with an unstable API that changes frequently. The maintainers explicitly encourage usage for testing and development but recommend caution in mission-critical environments until the API stabilizes. Development activity shows consistent engagement with the codebase, regular updates to address issues and features, and responsiveness to community contributions. The project maintains comprehensive documentation including a user guide and API reference, indicating a commitment to helping users understand and adopt the operator effectively.