Features of odo
odo, application developers can develop, test, debug, and deploy microservices based applications on Kubernetes without having a deep understanding of the platform.
odo follows create and push workflow. As a user, when you create, the information (or manifest) is stored in a configuration file. When you push it gets created on the Kubernetes cluster. All of this gets stored in the Kubernetes API for seamless accessibility and function.
odo uses deploy and link commands to link components and services together.
odo achieves this by creating and deploying services based on Kubernetes Operators in the cluster. Services can be created using any of the operators available on OperatorHub.io. Upon linking this service,
odo injects the service configuration into the service. Your application can then use this configuration to communicate with the Operator backed service.
Below is a summary of what
odo can do with your Kubernetes cluster:
- Create a new manifest or existing one to deploy applications on Kubernetes cluster
- Provide commands to create and update the manifest without diving into Kubernetes configuration files
- Securely expose the application running on Kubernetes cluster to access it from developer's machine
- Add and remove additional storage to the application on Kubernetes cluster
- Create Operator backed services and link with them
- Create a link between multiple microservices deployed as
- Debug remote applications deployed using
odofrom the IDE
- Run tests on the applications deployed on Kubernetes
Take a look at the "Using odo" documentation for in-depth guides on doing advanced commands with
What features to expect in odo?
For a quick high level summary of the features we are planning to add, take a look at odo's milestones on GitHub.