konveyor/operator

Konveyor is an open-source project that gives developers and platform teams visibility, analysis, and transformation tools to predictably re-platform and...

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓

konveyor/operator has 30+ stars and 40+ forks on GitHub, is written in Jinja, and was last pushed on Oct 16, 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 February 17th, 2022
Open Issues & Pull Requests: 19 (+0)
GitHub issues: Enabled
Number of forks: 49
Total Stargazers: 38 (+0)
Total Subscribers: 12 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.6 hours
Mean response time: 41.3 days
90th percentile: 144.8 days
Tracked items: 55

Maintainer activity

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

At least 86% of operator's 7 maintainers work at Red Hat. 6 say where they work, and 6 of those are Red Hat.

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.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 11
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 172 days
Stale 30+ days: 8
Stale 90+ days: 6

Recent activity

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

Top labels

  • needs-triage (43)
  • needs-priority (42)
  • needs-kind (40)
  • triage/accepted (15)
  • kind/documentation (6)
  • priority/important-longterm (6)
  • kind/feature (5)
  • stale (5)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Konveyor Operator is a Kubernetes operator that manages the deployment and lifecycle of Konveyor on Kubernetes and OpenShift clusters.

Konveyor addresses the challenge of migrating and refactoring legacy applications to run on Kubernetes and cloud-native platforms at scale. The operator automates the installation and ongoing management of Konveyor's analysis and transformation tools, eliminating manual configuration overhead. It handles resource provisioning, updates, and operational concerns so teams can focus on application modernization rather than infrastructure management.

Organizations should adopt this operator if they are running Kubernetes 1.25 or later or OpenShift 4.12 or later and need to manage Konveyor deployments across multiple clusters or environments. It suits teams undertaking large-scale application re-platforming efforts who want consistent, repeatable deployments. The operator requires Operator Lifecycle Manager support, persistent storage, ingress capabilities, and network policy support. By default, it enforces namespace network isolation through NetworkPolicy resources, restricting egress to cluster DNS, in-namespace traffic, and specific ports for external communication. Teams using non-standard ports for proxies, git repositories, artifact repositories, or other external systems will need to adjust the default network policies to allow those connections.

The project maintains active development with regular updates to support new Kubernetes and OpenShift versions. The operator is actively refined based on real-world deployment scenarios, as evidenced by detailed handling of network policy edge cases and support for various artifact repository configurations. The team responds to operational requirements encountered in production environments, incorporating feedback into the operator's default behaviors and documentation.