Helm is the CNCF-graduated package manager for Kubernetes, shipping as a single Go CLI binary (cmd/helm/helm.go) built on the Cobra command framework. In production it packages applications as "charts" — versioned bundles of templated Kubernetes manifests — and manages their full lifecycle: install, upgrade, rollback, uninstall, and release testing. Release state is persisted in pluggable storage drivers: Kubernetes Secrets, ConfigMaps, in-memory, or SQL (PostgreSQL). It also handles chart repository management, dependency resolution with lock files, OCI registry push/pull, plugin installation (subprocess and WASM/Extism runtimes), and PGP-style provenance signing/verification of chart tarballs. The architecture is a layered Go monolith: pkg/cmd defines ~40 Cobra subcommands that delegate to pkg/action business-logic objects (Install, Upgrade, Rollback, List, Status, etc.); pkg/engine renders Go templates against coalesced chart values; pkg/kube wraps k8s.io/client-go for resource apply/delete with readiness waiting and retrying round-trippers; pkg/registry implements an OCI client via ORAS; internal/plugin provides an extensible plugin system with subprocess and Extism (WASM) runtimes; pkg/provenance handles cryptographic chart signing. Chart APIs are versioned — a public v2 API (pkg/chart/v2) coexists with a gated v3 API (internal/chart/v3), and release records have v1/v2 variants behind accessor interfaces — a deliberate compatibility strategy that introduces some code duplication. The primary data flow is: chart archive (tgz from a repository, local path, or OCI artifact) → chart loader with path-traversal and decompression-size guards → value coalescing (user overrides merged over chart defaults with subchart scoping) → Go template engine with Sprig-style functions → validated YAML manifests → Kubernetes API via client-go; the resulting release record is gzip+base64 encoded into the storage backend. External dependencies are the Kubernetes API server, HTTP/HTTPS chart repositories, OCI registries, and GnuPG-compatible keyrings. The main structural debt is the intentional v2/v3 migration duplication (internal/storage/driver and internal/chart/v3 mirror their public pkg/ counterparts) plus legacy compatibility paths such as requirements.yaml and deprecated boolean --dry-run flags. This is purely an application repository with no data-research character.
Harbor is an open-source, cloud-native container registry platform for managing OCI/Docker images, Helm charts, and other artifacts. It provides a full-stack solution with a Go backend, Angular web portal, PostgreSQL database, and Redis/ValKey job queue. The system supports artifact storage, vulnerability scanning (Trivy integration), SBOM generation, multi-registry replication (Docker Hub, Quay, JFrog, cloud CRs), tag retention policies, immutable tags, RBAC with LDAP/OIDC, robot accounts, webhook/notification pipelines, P2P preheat, and audit logging. The architecture follows a layered pattern: REST API handlers (v2.0) → controllers → managers → DAOs, with middleware chains for security, quota, and content trust. Key entry points include the core API server, job service for background tasks, registry controller for blob/manifest management, and the Angular portal for administration. External dependencies include PostgreSQL, Redis, Trivy scanner, and various cloud registry APIs. The codebase is well-structured with extensive unit and integration tests, though it exhibits some technical debt from generated mocks and legacy components.
This repository is the official Helm chart collection for deploying Kong API Gateway and related operators (Kong Ingress Controller, Kong Gateway Operator, Kong Operator, Kong AI Gateway) on Kubernetes. It provides production-grade deployment templates with support for DB-less, PostgreSQL, hybrid mode, enterprise features, cert-manager integration, Prometheus monitoring, and admission webhooks. The architecture is a multi-chart Helm repository with subcharts for CRDs (kic-crds, gwapi-crds, ko-crds) and extensive CI snapshot testing via helm-chartsnap. Key entry points include the main `charts/kong/` chart for the gateway and ingress controller, `charts/kong-operator/` for the Kong Operator managing Konnect and AI gateway resources, and `charts/gateway-operator/` for the Gateway API operator. External dependencies include Kong container images, cert-manager, Bitnami PostgreSQL (optional), and Konnect SaaS for enterprise deployments. The repository is actively maintained with regular releases, changelogs, and upgrade guides, though CRDs are auto-generated and may drift from upstream operator versions.
Fluid is a Kubernetes-native operator for orchestrating distributed data caching and acceleration. It manages multiple cache runtimes (Alluxio, Jindo, JuiceFS, EFC, Thin, Vineyard, CacheRuntime) as custom resources, providing dataset abstraction, automated data operations (DataLoad, DataBackup, DataMigrate, DataProcess), and transparent FUSE mount injection via a CSI driver and mutating webhook. The system comprises several controller binaries, a CSI plugin, and a webhook server, all deployed via Helm charts. The architecture uses a common base engine interface with per-runtime implementations, a template engine for lifecycle management, and extensive utility packages for Kubernetes client operations, port allocation, security filtering, and monitoring.
This repository provides a Helm chart for deploying Uptime-Kuma, a self-hosted uptime monitoring tool, on Kubernetes. The chart is well-structured with support for Deployment or StatefulSet, persistent storage, ingress, external database (MariaDB/MySQL), Prometheus ServiceMonitor, and network policies. It includes comprehensive helm-unittest tests, CI/CD pipelines for linting, testing, and releasing, and automated dependency updates via Renovate. The chart is actively maintained and follows Helm best practices.
This repository provides deployment and configuration artifacts for Mend Renovate Self-Hosted, a commercial offering that wraps the open-source Renovate dependency update tool. It contains Helm charts for both Community and Enterprise editions, Docker Compose examples, environment variable references, TLS configuration templates, and OpenAPI specifications for the management API. The actual application code (server, worker, web UI) is distributed as pre-built Docker images and is not present in this repo. The system operates as a distributed job queue: a server schedules and enqueues dependency update jobs, workers execute Renovate CLI runs, and an optional web UI provides administrative dashboards. Enterprise features include worker queue isolation, Kafka event notifications, RBAC, and enhanced reporting (LibYears, pull request stats). The repository is well-documented with clear setup guides for GitHub, GitLab, and Bitbucket Data Center, and includes CI/CD workflows for linting and releasing Helm charts. While the repo contains no application source code, its deployment artifacts are professionally structured and follow best practices for extensibility (e.g., extra manifests, worker pool templates).
This repository is the official Helm chart distribution hub for Grafana's observability stack, containing over 20 charts for deploying Loki, Tempo, Mimir, Promtail, Grafana Agent, enterprise metrics/logs, and supporting components (rollout-operator, pdc-agent, snyk-exporter, etc.) on Kubernetes. The codebase is entirely Helm templates, values files, CRDs, and CI/CD scripts—no application source code. The architecture follows standard Helm patterns with per-component subdirectories, shared helpers, and extensive use of conditional logic for enterprise features, scaling, and storage backends. Many charts are deprecated or have their source maintained in separate product repositories (e.g., grafana/loki, grafana/tempo), with releases still published here. The repository shows signs of technical drift (old API versions, duplicated template logic, legacy dependencies) but remains actively maintained for the remaining non-deprecated charts with recent CI updates and release automation. It serves as both a legacy archive and an active distribution point.