# Install litmusctl with Homebrew, Nix Command-line interface for interacting with LitmusChaos. Version 1.27.0 via Homebrew; verified 2026-07-26. Also installable with nix: nix profile install nixpkgs#litmusctl. ## Install ```sh sudo av install brew:litmusctl ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install litmusctl ``` Evidence: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#litmusctl ``` Evidence: nixpkgs package indexes: pkgs/by-name/li/litmusctl/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ## Package facts - **Package key:** brew:litmusctl - **Package manager:** Homebrew - **Version:** 1.27.0 - **Source summary:** Command-line interface for interacting with LitmusChaos - **Homepage:** - **Repository:** - **Last updated:** 2026-07-26T13:41:02+02:00 - **Generated:** 2026-08-03T19:37:03+00:00 ## Executables - litmusctl (alias) ## Install behavior - Bottle: not available ## Freshness - Page generated: 2026-08-03 - Package-manager version: 1.27.0 ## Project history and usage litmusctl is the command-line companion to LitmusChaos, a CNCF-hosted cloud-native chaos engineering platform. It matters less as a standalone tool than as the terminal interface for connecting Chaos Delegates, creating projects, scheduling Chaos Scenarios, and managing LitmusChaos accounts. ### Project history LitmusChaos began as Kubernetes-oriented chaos engineering tooling before becoming a CNCF project. The separate litmusctl repository was created on February 15, 2021, after Litmus had already entered CNCF Sandbox, giving operators a Go-based CLI for the agent-plane workflows around Litmus ChaosCenter and Kubernetes clusters. The litmusctl README documents versioned usage guides spanning early v0.2-era compatibility through later v0.12-v0.23 and 1.x releases, which reflects its role as a compatibility-sensitive operations tool tied to LitmusChaos control-plane versions. ### Adoption history Litmus itself was accepted into CNCF on June 25, 2020 and moved to Incubating on January 11, 2022. That CNCF path gave the surrounding tools, including litmusctl, a place in cloud-native SRE workflows rather than only in vendor-specific chaos demos. The broader Litmus project advertises adopters and end-user case studies, while litmusctl adoption is mostly implicit: users who run LitmusChaos in Kubernetes clusters need a supported CLI path for delegate connection and account operations. ### How it is used litmusctl is used to connect Chaos Delegates, create projects, schedule Chaos Scenarios, disconnect delegates, and manage multiple LitmusChaos accounts. Its documented requirements include a kubeconfig at ~/.kube/config and kubectl underneath for applying manifests. For package users, the key operational detail is version compatibility: the README maps litmusctl releases such as 1.19.0 through 1.26.0 to supported Chaos Center version ranges. ### Why package nerds care For Homebrew and Nix users, litmusctl is a small example of a cloud-native project's operational surface being shipped as a standalone CLI, separate from the heavier Kubernetes control plane it manages. It also shows the package-manager problem of distributing fast-moving Kubernetes ecosystem CLIs whose usefulness depends on a compatibility matrix rather than only on their own version number. ### Timeline - 2017: LitmusChaos work began as simple Kubernetes chaos jobs, according to CNCF project history. - 2020-06-25: Litmus was accepted into CNCF. - 2021-02-15: The litmuschaos/litmusctl GitHub repository was created. - 2022-01-11: Litmus moved to CNCF Incubating. - 2026-05-20: The litmusctl repository listed release 1.26.0. ### Related projects - LitmusChaos is the parent chaos engineering platform; ChaosHub provides reusable chaos experiments; kubectl and Kubernetes are required context for delegate installation and cluster operations. ### Sources - - - - - ## Security Notes No matching local secret-handling manifest was found for litmusctl. Nucleus package metadata is still published here so future coverage has a stable package URL. ## 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 ## Other Package-Manager Records - Nix - litmusctl: normalized package name match | nixpkgs package indexes: pkgs/by-name/li/litmusctl/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/litmusctl.yml](https://github.com/mxcl/pkgdb/blob/main/combined/litmusctl.yml) ## Sources - 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