6c1c8b2a19
* Update introduction message in Deploy guide * Fix syntax highlighting for Shell commands * Bump PrismJS to 1.29.0 to have syntax highlighting for things like Dockerfiles * Enable syntax highlighting for Dockerfile content in the Deploy guides * Update instructions on how to login to the container registry * Add instructions on how to register the image registry in odo This is to be able to use image selectors. * Use a relative image name in the Devfile * Add comment about the ingress domain name variable * Update the deploy guide for .NET * Highlight items that need to be changed in the Devfile * Register the image registry first and make it clear that permissions might need to be updated To make things simple, use a public registry like ttl.sh that does not require authentication. * Add more details on how to access the application
odo - Developer-focused CLI for fast & iterative application development on Kubernetes
Overview
odo is a fast, and iterative CLI tool for developers who write, build, and deploy applications on Kubernetes and OpenShift.
Why use odo?
- 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 Kubernetes API. There is no requirement for a daemon or server process. - 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 both 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.
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.