Automic VaultAutomic Vault

brew

Installer kops avec Homebrew, MacPorts, Nix, scoop

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de kops pour les workflows d'agents IA.

installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%
brew install kops

local Homebrew formula metadata

MacPortsvérifié · 94%
sudo port install kops

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

Windows

Scoopvérifié · 92%
scoop install main/kops

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

aperçu

Résumé du paquet

Production Grade K8s Installation, Upgrades, and Management

Commandes et alias

  • kops

historique

Historique du projet et usages

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.

Historique du projet

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.

Historique d'adoption

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.

Modes d'utilisation

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.

Pourquoi les passionnés de paquets s'y intéressent

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.

Chronologie

  • 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.

posture de sécurité

Niveau de risque : vert

narrow executable package without higher-risk signals.

Classificateur de risque

risque vert · confiance faible · appliance

Pourquoi

  • narrow executable package without higher-risk signals

Signaux

  • metadata:no-higher-risk-signals

Comportement d'installation

  • Aucun hook post-install Homebrew n’est enregistré dans les métadonnées de formule.
  • Les métadonnées de bottle Homebrew sont disponibles pour 6 plateformes.
  • S’installe avec 1 dépendances d’exécution.
  • Les métadonnées de compilation listent 1 dépendances de compilation.

Revue recommandée

Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des plugins.

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

exécutables

Exécutables installés

CommandeTypeExpositionNote
kopscliexécutable global

fraîcheur

Version et fraîcheur

Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.

page générée2026-07-25
version du gestionnaire1.36.0
gestionnaire mis à jour2026-07-15
données localesOK
amontà jour
dernière version détectéev1.36.0

https://github.com/kubernetes/kops

  • OKAucun avertissement de fraîcheur n'a été généré.

métadonnées d'installation

Métadonnées du paquet

Clé du paquetbrew:kops
Version1.36.0
Gestionnaire de paquetsHomebrew
Page du gestionnaire de paquetshttps://formulae.brew.sh/formula/kops
Page d'accueilhttps://kops.sigs.k8s.io/
Dépôthttps://github.com/kubernetes/kops
Docs amonthttps://kops.sigs.k8s.io/
LicenceApache-2.0
Archive sourcehttps://github.com/kubernetes/kops/archive/refs/tags/v1.36.0.tar.gz
Dernière mise à jour2026-07-15T20:53:48Z
Pulseupdated
Dépendanceskubernetes-cli
Dépendances de compilationgo
Bouteilledisponible (sur arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux)
post-install Homebrewnon défini
Serviceaucun déclaré

faits du registre

Détails de la base source

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

correspondances dans les bases sources

Autres enregistrements de gestionnaires de paquets

Les correspondances proviennent d’index externes de gestionnaires de paquets et restent séparées des liens de paquets Automic Vault locaux.

Nix95%

kops

nix profile install nixpkgs#kops
  • normalized package name match
  • Correspondance par : 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
  • Correspondance par : 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
  • Correspondance par : 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

piste source

Généré depuis les données du dépôt

Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.

Sources utilisées

  • 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