Automic VaultAutomic Vault

brew

Install cloud-provider-kind with Homebrew, Nix

Cloud provider for KIND clusters. Version 0.11.1 via Homebrew; verified 2026-06-26.

install

Additional install commands

macOS

Homebrewverified · 100%
brew install cloud-provider-kind

local Homebrew formula metadata

Linux

Nixverified · 92%
nix profile install nixpkgs#cloud-provider-kind

nixpkgs package indexes · pkgs/by-name/cl/cloud-provider-kind/package.nix · source: api.github.com

overview

Package summary

Cloud provider for KIND clusters

Commands and aliases

  • cloud-provider-kind

history

Project history and usage

cloud-provider-kind is a Kubernetes SIGs project that gives kind clusters a local cloud-provider-style LoadBalancer experience. It is newer and narrower than kind itself, but its official docs provide enough source-backed context for package history.

Project history

The kubernetes-sigs/cloud-provider-kind repository was created in 2023 to fill a specific gap in kind-based testing: kind is useful for cheap local Kubernetes clusters, but does not itself provide all behavior that depends on cloud providers, especially LoadBalancer services.

The README documents the provider as a local controller that watches kind clusters and LoadBalancer Services, then creates corresponding containers to expose those Services. It also added a published controller-manager image starting with v0.4.0.

Adoption history

Official installation paths include `go install`, building from source, Docker, and community-supported Homebrew packaging. The README explicitly says package-manager builds are community supported and not produced by the maintainers.

The project gained visible Kubernetes community attention through a KubeCon EU 2024 talk linked from the README, which is meaningful adoption evidence for a Kubernetes SIG utility.

How it is used

Users create a kind cluster, run `cloud-provider-kind` in a terminal, and then create LoadBalancer Services or Gateway API resources that the provider exposes through local containers.

The provider also supports Gateway API behavior and a registry override environment variable for mirroring its proxy image.

Why package nerds care

For package maintainers, cloud-provider-kind is interesting because upstream treats Homebrew as a community package while Go install and container images remain closer to the project. That split matters for users who expect Kubernetes SIG artifacts to be canonical.

It is also a small but useful example of packaging local Kubernetes infrastructure behavior as a single CLI.

Timeline

  • 2023: kubernetes-sigs/cloud-provider-kind GitHub repository metadata was created.
  • v0.4.0: The README records availability of the registry.k8s.io controller-manager image.
  • 2024: The README links a KubeCon EU talk about load balancing on kind.

Related projects

  • kind is the local Kubernetes cluster tool that cloud-provider-kind extends.
  • Kubernetes Gateway API is supported by cloud-provider-kind.
  • Kubernetes cloud-provider implementations are the broader family of projects whose behavior this tool emulates locally.

security posture

Risk level: orange

infrastructure mutation or orchestration signal.

Risk classifier

orange risk · medium confidence · infrastructure

Why

  • infrastructure mutation or orchestration signal

Signals

  • text:cluster,cloud

Install behavior

  • No Homebrew post-install hook is recorded in formula metadata.
  • Homebrew bottle metadata is available for 6 platform targets.
  • Build metadata lists 1 build dependencies.

Recommended review

Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.

executables

Installed executables

CommandKindExposureNote
cloud-provider-kindcliglobal executable

freshness

Version and freshness

These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.

page generated2026-07-08
manager version0.11.1
manager updated2026-06-26
local dataok
upstreamcurrent
latest detectedv0.11.1

https://github.com/kubernetes-sigs/cloud-provider-kind

  • okNo freshness warnings were generated.

install metadata

Package metadata

Package keybrew:cloud-provider-kind
Version0.11.1
Package managerHomebrew
Package manager pagehttps://formulae.brew.sh/formula/cloud-provider-kind
Homepagehttps://kubernetes-sigs.github.io/cloud-provider-kind/
Repositoryhttps://github.com/kubernetes-sigs/cloud-provider-kind
Upstream docshttps://github.com/kubernetes-sigs/cloud-provider-kind#readme
LicenseApache-2.0
Source archivehttps://github.com/kubernetes-sigs/cloud-provider-kind/archive/refs/tags/v0.11.1.tar.gz
Last updated2026-06-26T13:38:33Z
Pulseupdated
Build dependenciesgo
Bottleavailable (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnot defined
Servicenone declared

registry facts

Source database details

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Namecloud-provider-kind
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

source database matches

Other package-manager records

Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.

Nix95%

cloud-provider-kind

nix profile install nixpkgs#cloud-provider-kind
  • normalized package name match
  • Matched by: Cloud Provider Kind
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/cl/cloud-provider-kind/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

source trail

Generated from repository data

This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.

Used sources

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment