Ross ROSS = Recommend OSS · open-source software intelligence for agents

keel-hq/keel

Kubernetes Operator to automate Helm, DaemonSet, StatefulSet & Deployment updates observed · 2026-08-28

github.com/keel-hq/keel · homepage · Go · MPL-2.0 (copyleft) observed · 2026-08-28

Health v2 · maintenance only

94/100

  • Activity 98
  • Release rhythm 86
  • Longevity 100
How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.

  • gap_med: 32
  • age_days: 3371
  • days_rel: 19
  • days_push: 12
  • n_releases_24m: 8

Full methodology

Adoption not part of the score

2725 stars · 320 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

Keel is a lightweight, stateless Kubernetes operator that automatically updates Deployments, StatefulSets, DaemonSets, and Helm releases when new container images are available. It is configured entirely through annotations and labels in manifests or charts, with no CLI or API required, and supports semver-based update policies, registry webhooks, polling, approvals, and notifications.

Use cases

  • automatically update kubernetes deployments when a new docker image is pushed
  • auto-update helm releases with semver policies
  • poll container registries for new image tags and update workloads
  • handle dockerhub and quay webhooks to trigger cluster updates
  • require manual approval before deploying new image versions
  • get slack notifications when deployments are updated

When to choose

  • you want hands-off, policy-driven image updates in Kubernetes without a CLI or database
  • you prefer configuration via annotations in existing manifests or Helm charts
  • you need webhook, pubsub, or polling triggers from multiple container registries
  • you want lightweight self-hosted automation with Slack/Telegram/etc notifications and approvals

When to avoid

  • you need full GitOps with Git as the source of truth and drift reconciliation
  • you want manual control over every deployment rollout
  • you are not running Kubernetes or Helm workloads
  • you need complex multi-stage pipeline orchestration rather than simple image updates

Facets

service · maturity active

deployment container-orchestration workflow-automation webhook monitoring cloud-computing self-hosted go self-hosted cloud kubernetes-operator helm semver continuous-deployment image-updates registry-webhooks gitops-adjacent devops containers automation kubernetes docker

4 sources

Member repositories

RepositoryRoleHealth v2
keel-hq/keelmain94

For agents

markdown · JSON · MCP: product_card(name="keel-hq/keel")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem