Operations, observability, backup and security projects that earn trust under real load.
6 long-form field guideskubernetes / kubernetes
The famous repository rewards a slower reading. Its real subject is a durable API for declaring operational intent, then reconciling clusters toward that intent through many cooperating control loops.
aquasecurity / trivy
One command can cover packages, operating-system vulnerabilities, application dependencies, secrets, configuration and SBOM output. The difficult part begins when a finding needs evidence, ownership and a repair decision.
apache / airflow
Airflow lets teams define workflows as Python DAGs, schedule task instances, track state in a metadata database, and inspect runs through its user interface and APIs. It is powerful for finite, dependency-driven batch work, but adopting the repository also means owning a scheduler, execution layer, database, provider set, and upgrade process.
prometheus / prometheus
Its pull-based collection and PromQL are only half the design. The other half is restraint: labels need boundaries, alerts need meaning and local storage needs an honest retention plan.
opentofu / opentofu
The fork preserved a familiar configuration, provider and state model, then placed its future under community governance. The result is useful only when teams treat plans and state as serious operational assets.
grafana / grafana
Connecting a data source is easy. The harder work is preserving metric meaning, query cost, permissions, alert ownership and licensing clarity as dashboards become shared operational infrastructure.