# Install kustomizer with Homebrew

Package manager for distributing Kubernetes configuration as OCI artifacts. Version 2.2.1 via Homebrew; verified 2026-07-27.

## Install

```sh
sudo av install brew:kustomizer
```

Additional install commands:

### macOS

- Homebrew (100%):

```sh
brew install kustomizer
```

  Evidence: local Homebrew formula metadata

## Package facts

- **Package key:** brew:kustomizer
- **Package manager:** Homebrew
- **Version:** 2.2.1
- **Source summary:** Package manager for distributing Kubernetes configuration as OCI artifacts
- **Homepage:** <https://kustomizer.dev>
- **Repository:** <https://github.com/stefanprodan/kustomizer>
- **Last updated:** 2026-07-27T21:58:48+02:00
- **Generated:** 2026-08-03T19:37:03+00:00

## Executables

- kustomizer (alias)

## Install behavior

- Bottle: not available

## Freshness

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

Kustomizer is a Kubernetes configuration package manager built around the idea that manifests can be distributed as OCI artifacts in the same registries used for container images.

### Project history

The project was created by Stefan Prodan as an experimental package manager for publishing, fetching, diffing, customizing, validating, applying, and pruning Kubernetes resources. Its v2 line centered the tool on packaging Kubernetes configs as OCI artifacts, with signing through cosign and encryption through age.

### Adoption history

Kustomizer's adoption story is tied to Kubernetes supply-chain and GitOps workflows rather than to a broad plugin ecosystem. The v2.2.0 release explicitly added Flux v2-compatible OCI artifacts, and the official Flux guide shows a workflow where CI publishes an artifact and Flux pulls and reconciles it inside the cluster.

### How it is used

Users build and push Kubernetes manifests to OCI registries, tag and inspect artifacts, and apply those artifacts into clusters. The command reference and Flux guide emphasize registries such as GHCR, Docker Hub, ACR, ECR, GCR, Artifactory, and self-hosted registries.

### Why package nerds care

Kustomizer is notable because it treats Kubernetes configuration like a package artifact: content-addressed, signable, encryptable, and transportable through standard OCI registry infrastructure. That makes it part of the broader move to use OCI registries for more than container images.

### Timeline

- v2.0.0: Added OCI artifact distribution, push/pull, cosign verification, age encryption, and deployment from artifacts.
- v2.2.0: Added Flux v2-compatible OCI artifacts and an official Flux deployment guide.

### Related projects

- Kustomizer builds on Kubernetes server-side apply and overlaps operationally with Flux, kustomize, cosign, age, and OCI-compatible container registries.

### Sources

- <https://github.com/stefanprodan/kustomizer>
- <https://github.com/stefanprodan/kustomizer/releases/tag/v2.0.0>
- <https://github.com/stefanprodan/kustomizer/releases/tag/v2.2.0>
- <https://kustomizer.dev/guides/fluxcd/>


## Security Notes

infrastructure mutation or orchestration signal.

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


## Combined YAML source

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


## Sources

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