// the find
operator-framework/operator-sdk
SDK for building Kubernetes applications. Provides high level APIs, useful abstractions, and project scaffolding.
Operator SDK is the standard toolkit for building Kubernetes operators in Go, with additional support for Helm and Ansible. It sits on top of controller-runtime and kubebuilder, adding scaffolding, OLM integration, and a scoring/validation framework. If you're writing a production operator that needs to ship through OperatorHub, this is the path of least resistance.
The scaffolding generates a complete, idiomatic project structure including CRDs, RBAC markers, and reconciler boilerplate — you skip the part where you copy-paste from the kubebuilder book. OLM integration is deep: bundle generation, CSV scaffolding, and the `scorecard` test framework all work together, which matters if you're distributing through OperatorHub or OpenShift. The Helm operator mode lets you wrap an existing Helm chart as a Kubernetes operator without writing Go — useful for teams that own a chart but need lifecycle management in-cluster. Active release cadence (v1.42 with 40+ changelogs visible) means Kubernetes version support doesn't fall behind.
The GCR/kube-rbac-proxy migration warning right at the top of the README is a red flag for existing projects — upgrading requires replacing a sidecar that many operators depend on for metrics endpoint security, and the replacement approach (controller-runtime's WithAuthenticationAndAuthorization) is less documented. The abstraction stack is tall: your code sits on controller-runtime, which sits on client-go, and when things go wrong (watch cache staleness, leader election races, requeueing logic) you're debugging three layers deep with minimal help from the SDK. Testing support is thin — the scorecard runs basic checks but there's no first-class support for controller-level unit or integration testing beyond what envtest provides from kubebuilder, which requires running a real API server binary.