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

Leverage RHOAR in odo #333

Closed
slemeur opened this issue Apr 10, 2018 · 2 comments
Closed

Leverage RHOAR in odo #333

slemeur opened this issue Apr 10, 2018 · 2 comments
Labels
kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks triage/unresolved Indicates an issue that can not or will not be resolved. v2 Issue or PR that applies to the v2 of odo
Milestone

Comments

@slemeur
Copy link

slemeur commented Apr 10, 2018

Description

RHOAR provides application runtimes for OpenShift. Associated to the application runtimes, RHOAR provides a set of project templates which showcase how developers can use the application runtime for building fundamental blocks of cloud-native applications. (like creating RESTful APIs, implementing health checks, configmap or resiliency features like circuit breakers). . A complete experience is provided on https://developers.redhat.com/launch/.

Leveraging those application runtimes and project templates in odo would actually help developers to quickly bootstrap project (and new blocks of cloud native application), with an application runtime validated and productized by Red Hat offered through the Red Hat Container Catalog.

The goal of this epic is to define how RHOAR would be leveraged in odo

@slemeur slemeur 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 10, 2018
@kadel kadel added this to the J milestone Aug 7, 2018
@dharmit dharmit modified the milestones: J, backlog Dec 30, 2019
@cdrage
Copy link
Member

cdrage commented Feb 12, 2020

I have a feeling we're moving away from RHOAR and into using operators / something custom.

Could we close this @dharmit / @slemeur / @kadel ?

@girishramnani
Copy link
Contributor

yeah we are moving away from RHOAR and we have a PR which removes them from supported list #2729

@rm3l rm3l added the v2 Issue or PR that applies to the v2 of odo label Jun 16, 2023
@rm3l rm3l added the triage/unresolved Indicates an issue that can not or will not be resolved. label Jun 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/epic An issue categorized as a high-level Epic. Needs to be scoped and broken down in 1+ stories/tasks triage/unresolved Indicates an issue that can not or will not be resolved. v2 Issue or PR that applies to the v2 of odo
Projects
Archived in project
Development

No branches or pull requests

6 participants