Automic VaultAutomic Vault

brew

kops mit Homebrew, MacPorts, Nix, scoop installieren

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

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install kops

local Homebrew formula metadata

MacPortsverifiziert · 94%
sudo port install kops

MacPorts ports tree · devel/kops/Portfile · Quelle: api.github.com

Windows

Scoopverifiziert · 92%
scoop install main/kops

Scoop official bucket manifest trees · bucket/kops.json · Quelle: api.github.com

Überblick

Paketzusammenfassung

Production Grade K8s Installation, Upgrades, and Management

Befehle und Aliase

  • kops

Verlauf

Projektgeschichte und Nutzung

kOps, short for Kubernetes Operations, is one of the long-running Kubernetes cluster lifecycle tools. It is best known as a command-line way to create, upgrade, and maintain production-grade Kubernetes clusters while also provisioning the needed cloud infrastructure.

Projektgeschichte

The kOps repository was created under the Kubernetes GitHub organization on 2016-06-27, during the period when Kubernetes operators were still building practical tooling around cluster creation and upgrades. The README describes kOps as `kubectl` for clusters, reflecting its role as a higher-level administrative CLI rather than an application deployment tool.

Early release metadata shows v1.4.0-alpha.1 on 2016-09-08, with 1.4-era releases following in late 2016. The project then tracked Kubernetes minor versions closely enough that official docs describe a release cadence tied to Kubernetes releases, typically about a month later, after Kubernetes issues from a new version have had time to settle.

Adoptionsgeschichte

kOps became important because it filled a gap before managed Kubernetes offerings covered every common operational need. Its official support matrix grew around cloud targets including AWS and GCP, with additional providers such as DigitalOcean, Hetzner, OpenStack, and Azure documented at different support levels.

GitHub repository metadata observed on 2026-07-01 reported 16,632 stars and 4,710 forks, unusually high for an infrastructure lifecycle CLI. Its presence in Homebrew, MacPorts, Nix, and Scoop reflects a user base split across workstation operators and automation hosts.

Wie es verwendet wird

kOps is commonly used to create cluster specifications, store cluster state, provision cloud infrastructure, and perform Kubernetes upgrades. It also writes or relies on kubeconfig credentials, so package users tend to pair it with `kubectl` and cloud provider credentials.

For package-manager users, the value is that installing one CLI gives access to a whole cluster lifecycle workflow rather than only a client for an already-existing control plane.

Warum Paket-Nerds sich dafür interessieren

kOps is a classic Homebrew infrastructure formula: a single statically distributed CLI that hides a lot of distributed-systems machinery behind repeatable commands.

It also marks an era of Kubernetes packaging before every cloud had a polished managed-cluster console. Package indexes that carried kOps made serious Kubernetes cluster creation available from a developer laptop with one install command.

Zeitleiste

  • 2016-06-27: GitHub repository created under kubernetes/kops.
  • 2016-09-08: v1.4.0-alpha.1 appears in GitHub release metadata.
  • 2016-12-21: v1.4.4 release published.
  • 2026-07-01: GitHub repository metadata reported more than 16,000 stars and more than 4,700 forks.

Related projects

  • kOps is closely related to Kubernetes, kubectl, cloud provider CLIs, Terraform and CloudFormation workflows, and managed Kubernetes services.
  • Within Kubernetes tooling culture, it sits beside kubeadm, Cluster API, eksctl, and cloud-specific cluster provisioning tools.

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 6 Plattformziele verfügbar.
  • Installiert mit 1 Laufzeitabhängigkeiten.
  • Build-Metadaten listen 1 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

local files

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

Config paths the tool may read or write during local use.

Unix
{state store}/config

Credential files

Credential-bearing paths to review before unattended agent runs.

Unix
~/.kube/config

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
kopscliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-25
Manager-Version1.36.0
Manager aktualisiert2026-07-15
lokale DatenOK
Upstreamaktuell
neueste erkannte Versionv1.36.0

https://github.com/kubernetes/kops

  • OKEs wurden keine Aktualitätswarnungen generiert.

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:kops
Version1.36.0
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/kops
Homepagehttps://kops.sigs.k8s.io/
Repositoryhttps://github.com/kubernetes/kops
Upstream-Dokumentationhttps://kops.sigs.k8s.io/
LizenzApache-2.0
Quellarchivhttps://github.com/kubernetes/kops/archive/refs/tags/v1.36.0.tar.gz
Zuletzt aktualisiert2026-07-15T20:53:48Z
Pulseupdated
Abhängigkeitenkubernetes-cli
Build-Abhängigkeitengo
Bottleverfügbar (auf arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

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

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

kops

nix profile install nixpkgs#kops
  • normalized package name match
  • Abgeglichen nach: Kops
nixpkgs package indexes · raw.githubusercontent.com · nixpkgs package indexes: kops from https://raw.githubusercontent.com/NixOS/nixpkgs/master/pkgs/top-level/all-packages.nix
MacPorts95%

kops

sudo port install kops
  • normalized package name match
  • Abgeglichen nach: Kops
MacPorts ports tree · api.github.com · MacPorts ports tree: devel/kops/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1
Scoop95%

main/kops

scoop install main/kops
  • normalized package name match
  • Abgeglichen nach: Kops
Scoop official bucket manifest trees · api.github.com · Scoop official bucket manifest trees: bucket/kops.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

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