# kconf mit Homebrew, Nix installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für kconf in AI-Agent-Workflows.

## Installation

```sh
sudo av install brew:kconf
```

Weitere Installationsbefehle:

### macOS

- Homebrew (100%):

```sh
brew install kconf
```

  Evidenz: local Homebrew formula metadata

### Linux

- Nix (92%):

```sh
nix profile install nixpkgs#kconf
```

  Evidenz: nixpkgs package indexes: pkgs/by-name/kc/kconf/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1

## Paketfakten

- **Paketschlüssel:** brew:kconf
- **Paketmanager:** Homebrew
- **Version:** 2.0.0
- **Quellzusammenfassung:** CLI for managing multiple kubeconfigs
- **Homepage:** <https://github.com/particledecay/kconf>
- **Repository:** <https://github.com/particledecay/kconf>
- **Zuletzt aktualisiert:** 2026-07-27T21:58:38+02:00
- **Generiert:** 2026-08-03T19:37:03+00:00

## Executables

- kconf (Alias)

## Installationsverhalten

- Bottle: nicht verfügbar

## Version und Aktualität

- Seite generiert: 2026-08-03
- Manager-Version: 2.0.0
## Projektgeschichte und Nutzung

kconf is an opinionated command-line tool for managing multiple kubeconfig entries in the default Kubernetes config file.

### Projektgeschichte

The repository was created in January 2020. Its README explains the motivation as replacing shell automation around the KUBECONFIG environment variable with commands that merge, list, view, remove, and switch contexts in $HOME/.kube/config.

### Adoptionsgeschichte

The batch input records Homebrew and Nix packages. Upstream release history shows rapid 1.x releases during 2020 and a 2.0.0 release on November 17, 2023.

### Wie es verwendet wird

kconf is used to add kubeconfig files, optionally rename contexts on import, list contexts, print one context's config, switch contexts, and set namespaces while leaving kubectl pointed at its default config path.

### Warum Paket-Nerds sich dafür interessieren

kconf is a small example of Kubernetes CLI tooling that wraps a common dotfile workflow instead of introducing a new service or database. Its package value is convenience: one executable for a task many operators otherwise solve with shell snippets.

### Zeitleiste

- 2020-01-14: GitHub repository created.
- 2020-01-21: v1.0.0 first stable release published.
- 2020-04-03: v1.1.2 added a view command for extracting a single kubeconfig.
- 2023-11-17: v2.0.0 release published.

### Related projects

- kconf's workflow is built around kubectl's default use of $HOME/.kube/config and the Kubernetes kubeconfig format.

### Quellen

- <https://github.com/particledecay/kconf>
- <https://github.com/particledecay/kconf/releases>
- <https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/>


## Sicherheitshinweise

narrow executable package without higher-risk signals.

- **Geiger-Risiko:** grün / niedrig
- narrow executable package without higher-risk signals


## Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.


## Configuration files

- Unix: ~/.kube/config

## Credential files

- Unix: ~/.kube/config
## Andere Paketmanager-Einträge

- Nix - kconf: normalized package name match | nixpkgs package indexes: pkgs/by-name/kc/kconf/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1


## Combined YAML source

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


## Quellen

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