odo
odo copied to clipboard
redhat-developer
Local development with Telepresence
/kind feature
User Story
As a developer I want to be able to debug part of my application locally So that I can take advantage of the tools that are locally available to me.
Developers should be able to setup a component to be run locally and have the traffic from the remote cluster to the local instance and proxy back the traffic to the remote service.
Links
- https://www.telepresence.io/
/kind feature
I think telepresence uses a totally opposite method then what odo provides.
odo tries to bring the user closer to the deployed service on cluster by making the inner loop faster.
telepresence and tools like https://github.com/eko/monday bring the cluster resources closer to the local application.
So I am not sure how we can support this approach with odo.
They are not too far off. Instead of setting up a pod on the cluster and syncing source files. odo sets up the same pod a bit different to sync the streams into that pod to local. The critical bits around devfile, services etc are essentially the same.
So if we think about this approach its like having a local mode where the application running outside of a container but even with that developers can link it with all the services running on cluster. Also I see the value of the features the odo provide like operator hub when doing local development. And local here doesn't mean docker. :+1: for this.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Now, when odo can run the application locally on podman we should start looking into this.
Enabling a scenario where a developer can run the application locally in a container using podman, and route cluster traffic to it would be a great fit for odo and it would make developing microservice applications easier.
A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}