operator-framework/operator-lifecycle-manager

A management framework for extending Kubernetes with Operators

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

operator-framework/operator-lifecycle-manager has 1.5k+ stars and 550+ forks on GitHub, is written in Go, and was last pushed on Oct 15, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 34 minutes ago
Added to GitGenius on October 15th, 2026
Created on August 11th, 2017
Open Issues & Pull Requests: 11 (+0)
GitHub issues: Enabled
Number of forks: 588
Total Stargazers: 1,866 (+0)
Total Subscribers: 50 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.0 days
Mean response time: 274.9 days
90th percentile: 1368.8 days
Tracked items: 244

Maintainer activity

1 person 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

Work labelled "kind/failing-test" is answered fastest, typically in under an hour, while "kind/feature" waits about 8 days. Three people close 93% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 95 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

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

Top labels

  • lifecycle/stale (188)
  • kind/bug (110)
  • kind/feature (73)
  • triage/unresolved (28)
  • triaged (27)
  • kind/flake (16)
  • kind/failing-test (10)
  • story (10)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Operator Lifecycle Manager is a Kubernetes operator that extends Kubernetes with a declarative system for installing, managing, and upgrading Operators and their dependencies across a cluster.

OLM solves the problem of managing Operators as first-class cluster extensions with the same sophistication applied to Kubernetes itself. It provides catalogs from which Operators can be discovered and installed, handles over-the-air updates through channels defined by maintainers, and enforces a dependency model so Operators can declare requirements on the platform or other Operators. The tool prevents API conflicts by requiring Operators to claim ownership of their custom resources, protecting cluster stability. It also annotates Operator APIs with descriptors that enable rich user interfaces in graphical consoles.

Adoption requires understanding that this project is in maintenance mode. The community is no longer accepting new features and will only address critical outage issues and emergent vulnerabilities on a best-effort basis. A successor design is under active development in a separate repository. Teams should evaluate whether the current feature set meets their needs or whether waiting for the new design is preferable. Existing clusters running OLM will continue to receive security updates, making it suitable for maintaining established Operator deployments, but new projects should consider the long-term implications of the maintenance status.

Development activity on the project is minimal and focused narrowly on stability. The team accepts only critical cluster-wide outages with no workaround, closes backlog issues that do not meet this threshold, and handles security vulnerabilities on a best-effort basis rather than with guaranteed response times.