# kubeone mit Homebrew, Nix, pacman, zypper installieren Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für kubeone in AI-Agent-Workflows. ## Installation ```sh sudo av install brew:kubeone ``` Weitere Installationsbefehle: ### macOS - Homebrew (100%): ```sh brew install kubeone ``` Evidenz: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#kubeone ``` Evidenz: nixpkgs package indexes: pkgs/by-name/ku/kubeone/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - pacman (92%): ```sh sudo pacman -S kubeone ``` Evidenz: Arch Linux sync databases: kubeone from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz - zypper (92%): ```sh sudo zypper install kubeone ``` Evidenz: openSUSE Tumbleweed package metadata: kubeone from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst ## Paketfakten - **Paketschlüssel:** brew:kubeone - **Paketmanager:** Homebrew - **Version:** 1.14.0 - **Quellzusammenfassung:** Automate cluster operations on all your environments - **Homepage:** - **Repository:** - **Zuletzt aktualisiert:** 2026-07-27T21:58:46+02:00 - **Generiert:** 2026-08-03T19:37:03+00:00 ## Executables - kubeone (Alias) ## Installationsverhalten - Bottle: nicht verfügbar ## Version und Aktualität - Seite generiert: 2026-08-03 - Manager-Version: 1.14.0 ## Projektgeschichte und Nutzung KubeOne is Kubermatic's open source Kubernetes cluster lifecycle CLI for installing, upgrading, repairing, and unprovisioning clusters across cloud, on-prem, edge, and IoT environments. The Homebrew package exposes the kubeone binary used by operators who want a declarative single-cluster management workflow. ### Projektgeschichte Kubermatic describes KubeOne as first released before KubeCon Barcelona in May 2019. By the August 18, 2020 KubeOne 1.0 announcement, the project had reached general availability after 15 months of development, 760 commits, and 600 GitHub stars, with a focus on automating highly available Kubernetes cluster operations. ### Adoptionsgeschichte KubeOne's adoption followed Kubermatic's broader hybrid and multi-cloud Kubernetes story: the docs emphasize native support for AWS, Azure, DigitalOcean, GCP, Hetzner Cloud, Nutanix, OpenStack, VMware Cloud Director, and VMware vSphere, plus integration with Terraform and Kubermatic machine-controller. ### Wie es verwendet wird Users define clusters declaratively in a YAML manifest, commonly named kubeone.yaml, then use kubeone commands to reconcile infrastructure-derived state, Kubernetes versions, addons, certificates, and worker nodes. The 1.0 release made the apply command central to provisioning, upgrades, repair, and disaster-recovery workflows. ### Warum Paket-Nerds sich dafür interessieren For package managers, KubeOne is notable because it packages an opinionated cluster lifecycle controller as a local CLI rather than a hosted service. It gives Homebrew users a repeatable binary for a workflow that spans Terraform output, Kubernetes APIs, SSH access, and cloud-provider assumptions. ### Zeitleiste - 2019-05: Kubermatic says KubeOne was first released before KubeCon Barcelona. - 2020-08-18: KubeOne 1.0 reached general availability. - 2020: KubeOne 1.0 introduced static worker nodes, flexible CNI deployment, and broader operating-system support. - 2026: KubeOne documentation listed maintained versioned docs through v1.13. ### Related projects - KubeOne is related to Kubermatic Kubernetes Platform, Terraform, Cluster API, Kubermatic machine-controller, kubeadm, and upstream Kubernetes conformance work. ### Quellen - - - - ## Sicherheitshinweise infrastructure mutation or orchestration signal. - **Geiger-Risiko:** orange / mittel - infrastructure mutation or orchestration signal ## 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: kubeone.yaml ## Andere Paketmanager-Einträge - Nix - kubeone: normalized package name match | nixpkgs package indexes: pkgs/by-name/ku/kubeone/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - pacman - kubeone - 1.12.3-3: normalized package name match | Arch Linux sync databases: kubeone from https://geo.mirror.pkgbuild.com/extra/os/x86_64/extra.db.tar.gz | A lifecycle management tool for Highly-Available Kubernetes clusters | https://github.com/kubermatic/kubeone - zypper - kubeone - 1.14.0-1.1: normalized package name match | openSUSE Tumbleweed package metadata: kubeone from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | CLI for the kubeone cluster automation | https://github.com/kubermatic/kubeone - zypper - kubeone-bash-completion - 1.14.0-1.1: normalized package name match | openSUSE Tumbleweed package metadata: kubeone-bash-completion from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | Bash Completion for kubeone | https://github.com/kubermatic/kubeone - zypper - kubeone-zsh-completion - 1.14.0-1.1: normalized package name match | openSUSE Tumbleweed package metadata: kubeone-zsh-completion from https://download.opensuse.org/tumbleweed/repo/oss/repodata/50b07339cb64c8ed4091bdbabddadc1ff5737b090e478818a195b40d8a3292861a879139b4a3987c31109699fde9fbf4a716367ddf4eef77da75f96e3193d6ed-primary.xml.zst | Zsh Completion for kubeone | https://github.com/kubermatic/kubeone ## Combined YAML source View the package source record on GitHub. [combined/kubeone.yml](https://github.com/mxcl/pkgdb/blob/main/combined/kubeone.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