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.

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

Advanced Usage: Flow from Podman to cluster #6861

Closed
Tracked by #6991
rm3l opened this issue Jun 1, 2023 · 2 comments
Closed
Tracked by #6991

Advanced Usage: Flow from Podman to cluster #6861

rm3l opened this issue Jun 1, 2023 · 2 comments
Labels
area/documentation Issues or PRs related to documentation or the 'odo.dev' website area/odo-on-podman Issues or PRs related to running odo against Podman kind/task Issue is actionable task lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@rm3l
Copy link
Member

rm3l commented Jun 1, 2023

Write a full guide for a typical development flow, i.e. that walks through the following:

  • initializing with odo init
  • starting a Dev session on Podman with no cluster required and iterating locally
  • adding support for Deploy in the Devfile
  • running the same application in production-like mode on Kubernetes/OpenShift (free Dev Sandbox) with odo deploy
@rm3l rm3l added area/documentation Issues or PRs related to documentation or the 'odo.dev' website area/odo-on-podman Issues or PRs related to running odo against Podman labels Jun 1, 2023
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Jun 1, 2023
@rm3l rm3l added kind/task Issue is actionable task and removed needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. labels Jun 1, 2023
Copy link
Contributor

github-actions bot commented Nov 3, 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 3, 2023
Copy link
Contributor

github-actions bot commented Dec 3, 2023

This issue was closed because it has been inactive for 30 days since being marked as stale.

@github-actions github-actions bot added the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Dec 3, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation Issues or PRs related to documentation or the 'odo.dev' website area/odo-on-podman Issues or PRs related to running odo against Podman kind/task Issue is actionable task lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
Archived in project
Development

No branches or pull requests

1 participant