# Installer odo-dev avec Homebrew, Nix, scoop Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de odo-dev pour les workflows d'agents IA. ## installation ```sh sudo av install brew:odo-dev ``` Commandes d'installation supplémentaires: ### macOS - Homebrew (100%): ```sh brew install odo-dev ``` Preuve: local Homebrew formula metadata ### Linux - Nix (92%): ```sh nix profile install nixpkgs#odo ``` Preuve: nixpkgs package indexes: pkgs/by-name/od/odo/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 ### Windows - Scoop (92%): ```sh scoop install main/odo ``` Preuve: Scoop official bucket manifest trees: bucket/odo.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 ## Faits du paquet - **Clé du paquet:** brew:odo-dev - **Gestionnaire de paquets:** Homebrew - **Version:** 3.16.1 - **Résumé source:** Developer-focused CLI for Kubernetes and OpenShift - **Page d'accueil:** - **Dépôt:** - **Dernière mise à jour:** 2026-07-17T17:20:41+09:00 - **Généré:** 2026-08-03T19:37:03+00:00 ## exécutables - odo (alias) ## Comportement d'installation - Bouteille: non disponible ## Version et fraîcheur - page générée: 2026-08-03 - version du gestionnaire: 3.16.1 ## Historique du projet et usages odo-dev is Homebrew's developer-oriented package for Red Hat's `odo`, a CLI for iterative container application development on OpenShift, Kubernetes, and later Podman. It should not be confused with `brew:odo`, the unrelated Atomic Object counter tool. ### Historique du projet The redhat-developer/odo repository was created on January 23, 2018. Red Hat's own deprecation article says odo was first released in 2019 as a simple, fast, developer-focused CLI intended to streamline the lifecycle of applications on OpenShift and Kubernetes without requiring developers to become cluster experts. odo evolved from an OpenShift developer convenience tool into an implementation of the open Devfile standard. The project README describes it as an iterative CLI for container-based application development that supports Podman, Kubernetes, and OpenShift, with automatic project detection, direct orchestrator API communication, and avoidance of hand-written Kubernetes YAML for common inner-loop work. Red Hat announced official deprecation on October 23, 2025. The deprecation notice set March 31, 2026 as the end-of-life date after which Red Hat would stop maintenance, security updates, and technical support, and it recommended OpenShift Dev Spaces for inner-loop development plus Podman and `oc` for outer-loop and cluster operations. ### Historique d'adoption odo's adoption was tied to Red Hat OpenShift documentation and the Devfile ecosystem. OpenShift docs presented it as a tool to create, develop, test, debug, and deploy microservice-based applications on OpenShift Container Platform and Kubernetes without deep platform knowledge. The same Red Hat deprecation article cited low adoption rates and limited community engagement as reasons to redirect resources. On July 1, 2026, the GitHub repository API showed 841 stars, 243 forks, and an archived repository, which matches the story of a serious vendor-backed tool that did not become the dominant Kubernetes developer interface. ### Modes d'utilisation Developers used `odo init`, `odo dev`, `odo deploy`, and related commands to create a Devfile-backed component, run or sync it into a development environment, and push resources into Kubernetes or OpenShift. Earlier OpenShift documentation described a create-and-push workflow in which local configuration produced resources stored through the Kubernetes API. In version 3, odo emphasized Devfile metadata, project analysis, Podman support for local workflows, and deployment paths that could target Kubernetes or OpenShift. Release notes around v3.9 and v3.10 show work on Pod Security Admission, Devfile `autoBuild` and `deployByDefault`, custom port mappings, Podman behavior, and `odo analyze` output. ### Pourquoi les passionnés de paquets s'y intéressent odo-dev matters in package metadata because its executable name collides with another Homebrew formula named `odo`. The formula name encodes the package-manager workaround: `odo-dev` installs Red Hat's OpenShift/Kubernetes developer CLI, while `odo` installs Atomic Object's atomic odometer. The package is also a good example of lifecycle metadata that package indexes need to retain. A CLI can remain installable after upstream deprecation, but history should explain why it existed, which workflows it served, and which replacements the maintainer recommended. ### Chronologie - January 23, 2018: The redhat-developer/odo GitHub repository was created. - 2019: Red Hat says odo was first released as a developer-focused CLI for OpenShift and Kubernetes application lifecycle work. - 2023-2024: The 3.x release line developed Devfile, Podman, Kubernetes, and OpenShift workflows, including Pod Security Admission and Devfile field support. - October 23, 2025: Red Hat announced official deprecation. - March 31, 2026: Red Hat's announced end-of-life date for maintenance, security updates, and technical support. ### Related projects - odo is related to OpenShift, Kubernetes, Podman, Devfile, OpenShift Dev Spaces, and the `oc` CLI. Red Hat's migration guidance explicitly mapped local container/image work toward Podman and cluster management toward `oc`. ### Sources - - - - - - - ## Notes de sécurité infrastructure mutation or orchestration signal. - **Risque Geiger:** orange / moyen - infrastructure mutation or orchestration signal ## Autres enregistrements de gestionnaires de paquets - Nix - odo: installed executable or alias match | nixpkgs package indexes: pkgs/by-name/od/odo/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1 - Scoop - main/odo: installed executable or alias match | Scoop official bucket manifest trees: bucket/odo.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 ## Combined YAML source View the package source record on GitHub. [combined/odo-dev.yml](https://github.com/mxcl/pkgdb/blob/main/combined/odo-dev.yml) ## Sources - pkg.so package database - Geiger risk classifier - curated package history - pkgdb category and tag curation - external package-manager database matches - cross-ecosystem install command graph