Need help with odo?
Click the “chat” button below for chat support from the developer who created it, or find similar developers for support.

About the developer

573 Stars 207 Forks Apache License 2.0 2.4K Commits 250 Opened issues


odo - Developer-focused CLI for OpenShift and Kubernetes

Services available


Need anything else?

Contributors list

[id="readme"] =

- Developer-focused CLI for Kubernetes and OpenShift :toc: macro :toc-title: :toclevels: 1[image:[GitHub release]][image:[Build Status]] image:[License]

[[overview]] == Overview

is a fast, iterative, and straightforward CLI tool for developers who write, build, and deploy applications on Kubernetes and OpenShift.

Existing tools such as

are more operations-focused and require a deep-understanding of Kubernetes and OpenShift concepts.
abstracts away complex Kubernetes and OpenShift concepts for the developer.

[[key-features]] == Key features

is designed to be simple and concise with the following key features:
  • Simple syntax and design centered around concepts familiar to developers, such as projects, applications, and components.
  • Completely client based. No additional server other than Kubernetes or OpenShift is required for deployment.
  • Official support for Node.js and Java components.
  • Detects changes to local code and deploys it to the cluster automatically, giving instant feedback to validate changes in real time.
  • Lists all the available components and services from the cluster.

[[core-concepts]] == Core concepts

Project:: A project is your source code, tests, and libraries organized in a separate single unit. Application:: An application is a program designed for end users. An application consists of multiple microservices or components that work individually to build the entire application. Examples of applications: e-Shop, Hotel Reservation System, Online Booking Component:: A component is a set of Kubernetes resources which host code or data. Each component can be run and deployed separately. Examples of components: Warehouse API Backend, Inventory API, Web Frontend, Payment Backend Service:: A service is software that your component links to or depends on. Examples of services: MariaDB, MySQL. Devfile:: A portable file responsible for your entire reproducible development environment.

[id="odo-supported-devfiles"] === Official Devfiles

Devfiles describe your development environment link. link:[Click here for more information on Devfile.]

.List of Devfiles which are officially supported by odo [options="header"] |=== |Language | Devfile Name | Description | Devfile Source | Supported Platform

| Java | java-maven | Upstream Maven and OpenJDK 11 | link:[java-maven/devfile.yaml] | amd64

| Java | java-openliberty | Open Liberty microservice in Java
| link:[java-openliberty/devfile.yaml] | amd64

| Java | java-quarkus | Upstream Quarkus with Java+GraalVM | link:[java-quarkus/devfile.yaml] | amd64

| Java | java-springboot | Spring Boot® using Java | link:[java-springboot/devfile.yaml] | amd64

| Node.JS | nodejs | Stack with NodeJS 12 | link:[nodejs/devfile.yaml] | amd64, s390x, ppc64le

|=== [id="odo-listing-available-images"] ==== Listing available Devfiles


The list of available Devfiles is sourced from the official link:[odo registry] as well as any other registries added via
odo registry add

To list the available Devfiles:

$ odo catalog list components Odo Devfile Components: NAME DESCRIPTION REGISTRY java-maven Upstream Maven and OpenJDK 11 DefaultDevfileRegistry java-openliberty Open Liberty microservice in Java DefaultDevfileRegistry java-quarkus Upstream Quarkus with Java+GraalVM DefaultDevfileRegistry java-springboot Spring Boot® using Java DefaultDevfileRegistry

nodejs Stack with NodeJS 12 DefaultDevfileRegistry

[[official-documentation]] == Official documentation

  • link:[Installing odo]
  • link:[Understanding odo]
  • link:[Deploying a devfile using odo]
  • link:[Devfile file reference]
  • link:[Debugging applications in odo]
  • link:[Managing environment variables]
  • link:[Configuring the odo CLI]
  • link:[Architecture of odo]
  • link:[odo CLI reference]
  • link:[Introduction to Operators]

[[installing-odo]] == Installing


To install on Linux / Windows / macOS follow our guide located on link:[]. All binaries and tarballs are synced between our link:[GitHub releases] and link:[OpenShift mirrors].

[[deploying-your-first-application]] == Deploying your first application

Click on the tutorial below to deploy your first


link:[Deploying a devfile using odo]

The following demonstration provides an overview of


[[contributing]] == Community, discussion, contribution, and support

=== Communication channels


  • For general help and inquiries, join our link:!forum/odo-users[odo-users Google group].
  • For any developmental discussion, use our link:!forum/odo-dev[odo-dev Google group].


All of our developer and user discussions happen in the link:[#odo channel on the official Kubernetes Slack].

If you haven't already joined the Kubernetes Slack, you can link:[invite yourself here].

Ask questions, inquire about odo or even discuss a new feature.


If you have an issue with

, please link:[file it].

Documentation Issues:

  • For any documentation issues on link:[] open a link:[GitHub issue with the documentation label].
  • If you have any documentation issues related to the link:[] site, file an issue in link:[Bugzilla]. Choose the OpenShift Container Platform product type and the Documentation component type.

=== Contributing Want to become a contributor and submit your code? Please have a look at our link:[Development Guide].

We work in 3-week sprint cycles. On a week when the sprint starts we have two planning calls:

  • "Sprint Planning Preparation and Issue Triage" - on Monday
  • "Sprint Planning" - on Wednesday

On top of our sprint planning calls, we have our regular "odo contributors call" (biweekly on Tuesdays). This is where we discuss technical challenges and anything related to odo development.

All our calls are open to public. You are welcome to join any of our calls.

You can find the exact dates of all scheduled odo calls together with sprint dates in the link: calendar.

To participate in the calls, please join link:!forum/odo-dev[odo-dev Google group]. When you join the group, you will automatically get invites to all odo related calls and get permissions to all necessary documents.

[[odo-roadmap]] == Roadmap for odo

Below is a roadmap for odo where 2.1, 2.2 and 2.3 are odo versions.

=== Post v2 (Before 19th Jan)

  • Refactor
  • Storage of linking info in devfile so that odo push can support this as well

=== 2.1 Planning (19th Jan - 13th April)

  • link:[#2756] - Add
    odo deploy
    command for initial transition from inner to outer loop
  • link:[#3026] - Support for Knative:Service (odo deploy)
  • link:[#3782] - Devfile support followup
  • link:[#2618] - Link via ServiceBindingRequest
  • link:[#2613] - Instantiate and manage services through Operator
  • link:[#4192] - Show components created by other tools in odo
  • link:[#3132] - control over how rsync and start/stop happens

=== 2.2 Planning

  • link:[#1238] - Integration with pipelines (CI)
  • link:[#4094] - Builds v2 Support (odo deploy should provide initial support for build v2 strategy)
  • link:[#2540] - e2e tests on windows & macOS

=== 2.3 Planning

  • link:[#3026] - Support for Knative Eventing
  • link:[#3664] - Add --now option support for Storage
  • link:[#3126] - allow
  • link:[#2191] - URL support for https

[[projects-using-odo]] == Projects using odo

These are some of the IDE plugins which use odo:

  • link:[VS Code Openshift Connector]
  • link:[Open VSX Openshift Connector]
  • link:[Openshift Connector for Intellij]
  • link:[Codewind for Eclipse Che]

[[experimental-mode]] == Experimental mode

Want to try out the odo experimental mode? Please read the link:[document] for more information.

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.