# Install operator-sdk with Homebrew, MacPorts, Nix, pacman, zypper

SDK for building Kubernetes applications. Version 1.42.3 via Homebrew; verified 2026-06-26. Also installable with nix: nix profile install nixpkgs#operator-sdk.

## Install

```sh
sudo av install brew:operator-sdk
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install operator-sdk
```

  Evidence: local Homebrew formula metadata

- MacPorts (94%):

```sh
sudo port install operator-sdk
```

  Evidence: MacPorts ports tree: devel/operator-sdk/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#operator-sdk
```

  Evidence: nixpkgs package indexes: pkgs/by-name/op/operator-sdk/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

- pacman (92%):

```sh
sudo pacman -S operator-sdk
```

  Evidence: Arch Linux sync databases: operator-sdk from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz

- zypper (92%):

```sh
sudo zypper install operator-sdk
```

  Evidence: openSUSE Tumbleweed package metadata: operator-sdk from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst

## Package facts

- **Package key:** brew:operator-sdk
- **Package manager:** Homebrew
- **Version:** 1.42.3
- **Source summary:** SDK for building Kubernetes applications
- **Homepage:** <https://sdk.operatorframework.io/>
- **Repository:** <https://github.com/operator-framework/operator-sdk>
- **Last updated:** 2026-06-26T21:39:12Z
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- helm-operator (alias)
- operator-sdk (alias)

## Install behavior

- Bottle: not available

## Freshness

- Page generated: 2026-08-03
- Package-manager version: 1.42.3
## Project history and usage

Operator SDK is the command-line and framework layer of the Kubernetes Operator Framework. It helps developers scaffold, build, test, package, and publish Operators: Kubernetes-native controllers that encode application operations such as install, upgrade, backup, failover, and day-two management.

### Project history

The Operator pattern was introduced by CoreOS in 2016 as a way to put human operational knowledge into Kubernetes controllers. Red Hat and the Kubernetes community announced the broader Operator Framework on 2018-05-01, with Operator SDK, Operator Lifecycle Manager, and metering as the original pillars.

Operator SDK's original role was to make controller development less repetitive: project scaffolding, custom resource definitions, generated manifests, build/test workflows, and common patterns over Kubernetes controller-runtime. The project later supported multiple authoring styles so teams could build Operators in Go, Ansible, or Helm depending on their operational logic and team skills.

Operator SDK reached v1.0 after almost two years of development, stabilizing around evolving Kubernetes extension APIs and best practices. CNCF accepted Operator Framework as an incubating project in 2020, which helped frame the SDK as part of a broader cloud-native ecosystem rather than only a Red Hat/OpenShift tool.

### Adoption history

Operator SDK spread because Kubernetes made custom controllers powerful but verbose. The SDK gave vendors and platform teams a repeatable way to create Operators for databases, storage systems, monitoring tools, security products, and application platforms while integrating with Operator Lifecycle Manager and OperatorHub distribution workflows.

Its adoption is tied to OpenShift and the wider OperatorHub ecosystem, but the SDK targets Kubernetes generally. Package managers carry it because developers often need the CLI locally to initialize projects, generate manifests, build bundles, run tests, and prepare operator metadata before pushing images or catalogs.

### How it is used

A typical user runs operator-sdk init, creates APIs and controllers or Helm/Ansible watches, writes reconciliation logic, generates CRDs and RBAC, builds a container image, and packages the result as an Operator bundle. Go users work close to controller-runtime; Helm and Ansible users wrap existing charts, roles, and playbooks in a Kubernetes reconciliation loop.

Cluster administrators usually encounter the output rather than the SDK itself: installable Operators, bundles, and catalog entries managed by OLM or related tooling.

### Why package nerds care

Operator SDK is important package-manager glue for Kubernetes developers because it turns a distributed-systems pattern into a local executable. Installing it gives a workstation the same scaffolding and bundle-generation behavior expected by CI pipelines and operator catalogs.

It also marks the moment Kubernetes packaging moved past YAML bundles: Operators became packages with controllers, CRDs, RBAC, lifecycle metadata, upgrade channels, and registry/catalog concerns.

### Timeline

- 2016: CoreOS introduces the Kubernetes Operator pattern.
- 2018-05-01: Red Hat announces the Operator Framework, including Operator SDK.
- 2020-07-09: CNCF announces Operator Framework as an incubating project.
- 2020: Operator SDK reaches v1.0 after almost two years of development.
- 2020s: Operator SDK continues to track Kubernetes, controller-runtime, Go, Helm, Ansible, OLM, and bundle-format changes.

### Related projects

- Operator SDK is related to Operator Framework, Operator Lifecycle Manager, OperatorHub, Kubebuilder, controller-runtime, Kubernetes CRDs, Helm, Ansible, OpenShift, and community-operators catalog repositories.

### Sources

- <https://github.com/operator-framework/operator-sdk>
- <https://operatorframework.io/>
- <https://sdk.operatorframework.io/>
- <https://sdk.operatorframework.io/docs/overview/>
- <https://www.cncf.io/blog/2020/07/09/toc-approves-operator-framework-as-incubating-project/>
- <https://www.redhat.com/en/blog/introducing-operator-framework-building-apps-kubernetes>
- <https://www.redhat.com/en/blog/operator-sdk-reaches-v1.0>


## Security Notes

infrastructure mutation or orchestration signal.

- **Geiger risk:** orange / medium
- infrastructure mutation or orchestration signal

## Other Package-Manager Records

- Nix - operator-sdk: normalized package name match | nixpkgs package indexes: pkgs/by-name/op/operator-sdk/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
- pacman - operator-sdk - 1.42.0-2: normalized package name match | Arch Linux sync databases: operator-sdk from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | SDK for building Kubernetes applications | https://github.com/operator-framework/operator-sdk
- zypper - operator-sdk - 1.42.3-1.3: normalized package name match | openSUSE Tumbleweed package metadata: operator-sdk from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | CLI for installing the Operator Lifecycle Manager | https://github.com/operator-framework/operator-sdk
- zypper - operator-sdk-bash-completion - 1.42.3-1.3: normalized package name match | openSUSE Tumbleweed package metadata: operator-sdk-bash-completion from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | Bash Completion for operator-sdk | https://github.com/operator-framework/operator-sdk
- zypper - operator-sdk-fish-completion - 1.42.3-1.3: normalized package name match | openSUSE Tumbleweed package metadata: operator-sdk-fish-completion from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | Fish Completion for operator-sdk | https://github.com/operator-framework/operator-sdk
- zypper - operator-sdk-zsh-completion - 1.42.3-1.3: normalized package name match | openSUSE Tumbleweed package metadata: operator-sdk-zsh-completion from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | Zsh Completion for operator-sdk | https://github.com/operator-framework/operator-sdk
- MacPorts - operator-sdk: normalized package name match | MacPorts ports tree: devel/operator-sdk/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1


## Combined YAML source

View the package source record on GitHub. [combined/operator-sdk.yml](https://github.com/mxcl/pkgdb/blob/main/combined/operator-sdk.yml)


## Sources

- pkg.so package database
- Geiger risk classifier
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph