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

odo dev must create PVCs for all volumes defined in the Devfile #6844

Open
feloy opened this issue May 25, 2023 · 4 comments
Open

odo dev must create PVCs for all volumes defined in the Devfile #6844

feloy opened this issue May 25, 2023 · 4 comments
Labels
area/dev Issues or PRs related to `odo dev` 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.

Comments

@feloy
Copy link
Contributor

feloy commented May 25, 2023 •
edited
Loading

/kind feature

Which functionality do you think we should add?

When running an Exec command inside a new container (uing a Job), the user may want to use a Persistent Volume. This persistent volume needs to be persistent across all commands during a Dev session. For this, odo dev needs to create PVCs for all volumes defined in the Devfile, so the Jobs can reuse these PVCs
@openshift-ci openshift-ci bot added the kind/feature Categorizes issue as a feature request. For PRs, that means that the PR is the implementation label May 25, 2023
@feloy feloy self-assigned this May 25, 2023
@github-actions github-actions bot added the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label May 25, 2023
@feloy feloy removed their assignment May 26, 2023
@github-actions
Copy link
Contributor

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 Aug 25, 2023
@github-actions
Copy link
Contributor

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 Sep 24, 2023
@github-project-automation github-project-automation bot moved this to Done ✅ in odo Project Sep 24, 2023
@rm3l
Copy link
Member

rm3l commented Sep 25, 2023

I think this is still relevant.

@rm3l rm3l reopened this Sep 25, 2023
@rm3l rm3l removed the status in odo Project Sep 25, 2023
@rm3l rm3l added area/dev Issues or PRs related to `odo dev` and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. labels Sep 25, 2023
@github-actions GitHub Actions
Copy link
Contributor

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 Dec 25, 2023
@github-actions github-actions bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 5, 2024
@rm3l rm3l added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Jan 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/dev Issues or PRs related to `odo dev` 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.
Projects
odo Project
Status: No status
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rm3l @feloy