Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Local development with Telepresence #2840

Open
gorkem opened this issue Apr 7, 2020 · 11 comments
Open

Local development with Telepresence #2840

gorkem opened this issue Apr 7, 2020 · 11 comments
Labels
kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@gorkem
Copy link
Contributor

gorkem commented Apr 7, 2020

/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

/kind feature
@openshift-ci-robot openshift-ci-robot added the kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation label Apr 7, 2020
@girishramnani girishramnani added the kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks label Apr 20, 2020
@girishramnani
Copy link
Contributor

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.

@girishramnani girishramnani added the triage/needs-information Indicates an issue needs more information in order to work on it. label Apr 20, 2020
@gorkem
Copy link
Contributor Author

gorkem commented Apr 22, 2020

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.

@girishramnani
Copy link
Contributor

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.
👍 for this.

@openshift-bot
Copy link

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

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 25, 2020
@girishramnani girishramnani added the priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done. label Nov 4, 2020
@deboer-tim
Copy link

Keeping this one fresh.
/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 30, 2020
@openshift-bot
Copy link

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

@openshift-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 28, 2021
@deboer-tim
Copy link

/remove-lifecycle stale

@openshift-ci-robot openshift-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 28, 2021
@openshift-bot
Copy link

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

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 30, 2021
@deboer-tim
Copy link

/remove-lifecycle stale

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 30, 2021
@kadel kadel added this to the 2.4 (planning) milestone Jun 16, 2021
@serenamarie125 serenamarie125 modified the milestones: 2.4 (planning), 2.5+ (planning) Sep 7, 2021
@rm3l rm3l removed this from the backlog (planning) milestone Sep 29, 2022
@rm3l rm3l added this to odo Project Oct 3, 2022
@rm3l rm3l moved this to To Do 📝 in odo Project Oct 3, 2022
@rm3l rm3l removed the status in odo Project Oct 3, 2022
@kadel
Copy link
Member

kadel commented Mar 10, 2023 •
edited
Loading

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.

@rm3l rm3l moved this to To Do 📝 in odo Project Jun 26, 2023
@rm3l rm3l removed the status in odo Project Jun 27, 2023
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Nov 4, 2023

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 github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 4, 2023
@rm3l rm3l added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/Low Nice to have issue. It's not immediately on the project roadmap to get it done. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
odo Project
Status: No status
Milestone
No milestone
Development

No branches or pull requests
8 participants
@kadel @gorkem @rm3l @openshift-bot @girishramnani @serenamarie125 @deboer-tim @openshift-ci-robot