Automic VaultAutomic Vault

brew

Installer liqoctl avec Homebrew

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

installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%
brew install liqoctl

local Homebrew formula metadata

aperçu

Résumé du paquet

Is a CLI tool to install and manage Liqo-enabled clusters

historique

Historique du projet et usages

liqoctl is the command-line entry point for installing and managing Liqo, an open-source Kubernetes multi-cluster project focused on resource sharing, workload offloading, inter-cluster networking, and storage across heterogeneous clusters.

Historique du projet

Liqo describes itself as an open-source project for dynamic and seamless Kubernetes multi-cluster topologies across on-premise, cloud, and edge infrastructures. The project states that it was kicked off at the Polytechnic University of Turin and is maintained by the Liqo community.

The CLI grew as the operational front door for that system: the documentation describes liqoctl as the tool used to install and manage Liqo-enabled clusters, with subcommands for install, peer, authenticate, offload, network, test, uninstall, and related cluster operations.

Historique d'adoption

Liqo's adoption evidence is clearest in Kubernetes-native contexts where teams want cluster peering and virtual-node style offloading without rewriting applications. Its public repository, documentation, Slack community, adopters file, and release assets show a project aimed at cloud, edge, research, and multi-cloud operators.

Homebrew packages the CLI as liqoctl, separating the operator-facing command from the broader Liqo repository and making the tool easy to install on macOS and Linux workstations used to administer Kubernetes clusters.

Modes d'utilisation

Operators use liqoctl to bootstrap Liqo into clusters, establish peerings, authenticate clusters, offload namespaces, inspect state, and remove Liqo resources. Its docs emphasize making multi-cluster behavior transparent to standard Kubernetes workloads.

The CLI is package-manager-friendly because it is a single Go-built executable that talks to Kubernetes APIs and controls cluster-side components rather than embedding a long-lived desktop service.

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

liqoctl is one of the newer wave of Kubernetes administrative CLIs that package managers carry so users can manage cloud-native infrastructure from a local shell. It sits near kubectl plugins, cluster lifecycle tools, and service-mesh CLIs in the package taxonomy.

For Homebrew users, it is notable because the formula packages a project-specific Kubernetes control plane tool rather than the server components themselves.

Chronologie

  • 2019: Liqo project copyright notices begin at 2019 on the official site and documentation.
  • 2021: Public Liqo discussion and early release activity centered on Kubernetes multi-cluster resource sharing.
  • 2026: Liqo v1.1.2 was published on GitHub on March 3, 2026, with liqoctl release assets for Linux and macOS.

Related projects

  • Liqo's repository notes code from Virtual Kubelet, which is conceptually related because Liqo represents remote cluster capacity through Kubernetes-native abstractions.
  • The broader neighborhood includes kubectl, Kubernetes Cluster API, service-mesh and multi-cluster networking projects, and GitOps tooling used to manage declarative multi-cluster topologies.

posture de sécurité

Niveau de risque : orange

infrastructure mutation or orchestration signal.

Classificateur de risque

risque orange · confiance moyen · infrastructure

Pourquoi

  • infrastructure mutation or orchestration signal

Signaux

  • text:cluster

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

exécutables

Exécutables installés

CommandeTypeExpositionNote
liqoctlcliexé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.2.0
gestionnaire mis à jour2026-07-03
données localesOK
amontà jour
dernière version détectéev1.2.0

https://github.com/liqotech/liqo

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

métadonnées d'installation

Métadonnées du paquet

Clé du paquetbrew:liqoctl
Version1.2.0
Gestionnaire de paquetsHomebrew
Page du gestionnaire de paquetshttps://formulae.brew.sh/formula/liqoctl
Page d'accueilhttps://liqo.io
Dépôthttps://github.com/liqotech/liqo
Docs amonthttps://docs.liqo.io/en/latest/usage/liqoctl/liqoctl.html
LicenceApache-2.0
Archive sourcehttps://github.com/liqotech/liqo/archive/refs/tags/v1.2.0.tar.gz
Dernière mise à jour2026-07-03T10:40:21Z
Pulseupdated
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 Nameliqoctl
Version Scheme0
Revision0
Head VersionHEAD
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • head
  • stable

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 package history
  • package relationship graph
  • package version freshness
  • package-page enrichment