b5ea6f144b
* Label ServiceBinding tests, so we can run them separately They require installing additional components in the cluster (OLM, SBO, ...). * Add GH Workflow for most of our tests (including cluster-related tests) This allows to easily test even multiple versions of Kubernetes if needed. For easier reporting and visualisation (and also avoid rebuilding odo many times), Podman tests have also been relocated in this same Workflow. Notes: I tried to spin up lightweight OpenShift clusters but gave up because of several issues: - MicroShift: I tried to use the aio container image, but this one is no longer maintained and is pretty old version of OCP. Trying to follow the official guidelines did not work either because a base RHEL OS is mandatory - CRC/OpenShiftLocal with Microshift preset: didnt pass the pre-checks because it detected an issue with nested virtualization on the GH Runner. * Drop unused code in helper_oc and use namespace instead of project When testing on Microshift, it seems that the Project API is purposely not implemented on MicroShift
odo - Fast, Iterative and Simplified container-based application development
Overview
odo is a fast, and iterative CLI tool for container-based application development.
It is an implementation of the open Devfile standard, supporting Podman, Kubernetes and OpenShift.
Why use odo?
- Easy onboarding: By auto-detecting the project source code, you can easily get started with
odo. - No cluster needed: With Podman support, having a Kubernetes cluster is not required to get started with
odo. Using a common abstraction,odocan run your application on Podman, Kubernetes or OpenShift. - Fast: Spend less time maintaining your application deployment infrastructure and more time coding. Immediately have your application running each time you save.
- Standalone:
odois a standalone tool that communicates directly with the container orchestrator API. - No configuration needed: There is no need to dive into complex Kubernetes YAML configuration files.
odoabstracts those concepts away and lets you focus on what matters most: code. - Containers first: We provide first class support for Podman, Kubernetes and OpenShift. Choose your favourite container orchestrator and develop your application.
- Easy to learn: Simple syntax and design centered around concepts familiar to developers, such as projects, applications, and components.
Learn more about the features provided by odo on odo.dev.
Demo
Installing odo
Please check the installation guide on odo.dev.
Official documentation
Visit odo.dev to learn more about odo.
Community, discussion, contribution, and support
Chat
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.
Issues
If you find an issue with odo, please file it here.
Contributing
- Code: We are currently working on updating our code contribution guide.
- Documentation: To contribute to the documentation, please have a look at our Documentation Guide.
We are an open community who welcomes any concerns, changes or ideas for odo! Come join the chat and hang out, ask or give feedback and just generally have a good time.
Meetings
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 team calls together with sprint dates in the google calendar (iCal format).
Legal
License
Unless otherwise stated (ex. /vendor files), all code is licensed under the Apache 2.0 License.
Usage data
When odo is ran for the first time, you will be asked to opt in to Red Hat's telemetry collection program.
With your approval, odo will collect pseudonymized usage data and send it to Red Hat servers to help improve our products and services. Read our privacy statement to learn more about it. For the specific data being collected and to configure this data collection process, see Usage data.