Skip to content

Issues: redhat-developer/odo

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

Clear current search query, filters, and sorts
12 Open 137 Closed
12 Open 137 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Create Backstage Plugin for Odo CLI to Bootstrap Application Development with Devfiles area/backstage Issues or PRs related to the Backstage integration 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/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)).
#7091 opened Sep 20, 2023 by mohitsuman
12 of 20 tasks
4
[Epic] Web UI as main odo interface kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#7002 opened Jul 24, 2023 by kadel
3 tasks
2
[Epic] Use odo with Podman (without Kubernetes/OpenShift cluster) [stage 4] area/odo-on-podman Issues or PRs related to running odo against Podman kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#6991 opened Jul 20, 2023 by rm3l
4 of 7 tasks
2
odo doctor as a diagnostic command to find issues that would prevent from making the most out of odo kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
#6661 opened Mar 15, 2023 by kadel
13 tasks
5
Pipeline as a code on IBMCloud for test area/infra Issues or PRs related to setting up or fixing things in infrastructure. Mostly CI infrastructure. area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one.
#6456 opened Jan 4, 2023 by anandrkskd
2
Automate command output in docs area/documentation Issues or PRs related to documentation or the 'odo.dev' website area/testing Issues or PRs related to testing, Quality Assurance or Quality Engineering estimated-size/M (10-20) Rough sizing for Epics. About 1 sprint of work for one person kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks 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.
#6192 opened Oct 4, 2022 by valaparthvi
5 of 27 tasks
7
odo catalog kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks 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.
#5523 opened Mar 7, 2022 by serenamarie125
3
Helm support on odo 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/Medium Nice to have issue. Getting it done before priority changes would be great.
#4236 opened Nov 18, 2020 by gorkem
13
Support for Knative Eventing kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks 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.
#3027 opened Apr 28, 2020 by sspeiche
3
Local development with Telepresence 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.
#2840 opened Apr 7, 2020 by gorkem
11
Use odo with OpenShift Service Mesh (aka Istio) area/openshift Issues or PRs related to OpenShift kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks 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.
#2623 opened Feb 20, 2020 by dudash
7
Integration with pipelines (CI) area/outerloop Issues or PRs related to outer-loop use cases 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. needs-triage Indicates an issue or PR lacks a `triage/*` and requires one.
#1238 opened Jan 27, 2019 by sspeiche
5
ProTip! Type g i on any issue or pull request to go back to the issue listing page.