Skip to content
Switch branches/tags
Go to file

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

odo - Developer-focused CLI for Kubernetes and OpenShift

GitHub release Build Status License


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

Existing tools such as kubectl and oc are more operations-focused and require a deep-understanding of Kubernetes and OpenShift concepts. odo abstracts away complex Kubernetes and OpenShift concepts for the developer.

Key features

odo 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


A project is your source code, tests, and libraries organized in a separate single unit.


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


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


A service is software that your component links to or depends on. Examples of services: MariaDB, MySQL.


A portable file responsible for your entire reproducible development environment.

Official Devfiles

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

Table 1. List of Devfiles which are officially supported by odo
Language Devfile Name Description Devfile Source Supported Platform



Upstream Maven and OpenJDK 11





Open Liberty microservice in Java





Upstream Quarkus with Java+GraalVM





Spring Boot® using Java





Stack with NodeJS 12


amd64, s390x, ppc64le

Listing available Devfiles


The list of available Devfiles is sourced from the official 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

Installing odo

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

Deploying your first application

Click on the tutorial below to deploy your first odo application:

The following demonstration provides an overview of odo:


Community, discussion, contribution, and support

Communication channels



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

If you haven’t already joined the Kubernetes Slack, you can invite yourself here.

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


If you have an issue with odo, please file it.

Documentation Issues:


Want to become a contributor and submit your code? Please have a look at our 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 odo calendar (iCal format).

To participate in the calls, please join 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.

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)

  • #2756 - Add odo deploy command for initial transition from inner to outer loop

  • #3026 - Support for Knative:Service (odo deploy)

  • #3782 - Devfile support followup

  • #2618 - Link via ServiceBindingRequest

  • #2613 - Instantiate and manage services through Operator

  • #4192 - Show components created by other tools in odo

  • #3132 - control over how rsync and start/stop happens

2.2 Planning

  • #1238 - Integration with pipelines (CI)

  • #4094 - Builds v2 Support (odo deploy should provide initial support for build v2 strategy)

  • #2540 - e2e tests on windows & macOS

2.3 Planning

  • #3026 - Support for Knative Eventing

  • #3664 - Add --now option support for Storage

  • #3126 - allow .devfile.yaml

  • #2191 - URL support for https

Experimental mode

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