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

update nodejs images in the supported component catalog #2603

Closed
4 tasks
girishramnani opened this issue Feb 14, 2020 · 10 comments · Fixed by #2729
Closed
4 tasks

update nodejs images in the supported component catalog #2603

girishramnani opened this issue Feb 14, 2020 · 10 comments · Fixed by #2729
Assignees
Labels
kind/user-story An issue of user-story kind priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)). v2 Issue or PR that applies to the v2 of odo
Projects

Comments

@girishramnani
Copy link
Contributor

User Story

As a developer I would like to use nodejs 12 images with all the features odo provides which includes experimental features like odo debug.

Acceptance Criteria

  • Basic features of odo should work correctly with new nodejs images (centos/nodejs-12-centos7, rhscl/nodejs-12-rhel7andnodeshift/centos7-s2i-nodejs`)
  • experimental features like odo debug should work correctly with new nodejs images
  • tests should all run against these new images and pass
  • It should show new nodejs images which are centos/nodejs-12-centos7, rhscl/nodejs-12-rhel7 and nodeshift/centos7-s2i-nodejs as supported images when ran odo catalog list components, But this should happen only when 3 ACs above are fulfilled.

Links

/kind user-story

@openshift-ci-robot openshift-ci-robot added the kind/user-story An issue of user-story kind label Feb 14, 2020
@girishramnani girishramnani changed the title add nodejs 12 images to supported images update nodejs images in the supported component catalog Feb 14, 2020
@kadel kadel added this to For consideration in Sprint 180 via automation Feb 14, 2020
@kadel
Copy link
Member

kadel commented Feb 14, 2020

/area s2i

@girishramnani girishramnani added the priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)). label Feb 18, 2020
@girishramnani girishramnani self-assigned this Feb 18, 2020
@girishramnani girishramnani moved this from For consideration to To do in Sprint 180 Feb 18, 2020
@girishramnani
Copy link
Contributor Author

I would need to verify that all of these images work in a sample nodejs application and using debug mode as well.
After that I would open a PR on odo-init-image to add the images in the supported list then a similar PR on this Repo.

@kadel
Copy link
Member

kadel commented Feb 19, 2020

▶ oc version
Client Version: 4.3.0-0.ci-2020-02-14-232526
Server Version: 4.3.0-0.ci-2020-02-14-232526
Kubernetes Version: v1.16.2
▶ oc get is nodejs -n openshift
NAME     IMAGE REPOSITORY                                                    TAGS                         UPDATED
nodejs   image-registry.openshift-image-registry.svc:5000/openshift/nodejs   10,10-SCL,8,8-RHOAR,latest   About an hour ago

@girishramnani girishramnani added the triage/needs-information Indicates an issue needs more information in order to work on it. label Feb 19, 2020
@kadel
Copy link
Member

kadel commented Feb 19, 2020

▶ oc get is nodejs -n openshift
NAME     IMAGE REPOSITORY                                                    TAGS           UPDATED
nodejs   image-registry.openshift-image-registry.svc:5000/openshift/nodejs   10,12,latest   55 minutes ago

▶ oc version
Client Version: 4.4.0-0.ci-2020-02-18-230529
Server Version: 4.4.0-0.ci-2020-02-18-230529
Kubernetes Version: v1.17.1

@lholmquist
Copy link

The nodeshift images mentioned above are no longer supported since we've migrated to using the images from rhscl

For our community examples, we've also moved from centos to ubi

@kadel
Copy link
Member

kadel commented Feb 25, 2020

The nodeshift images mentioned above are no longer supported since we've migrated to using the images from rhscl

For our community examples, we've also moved from centos to ubi

How about existing 3.11 clusters? Are those somehow updated to deprecate those images?

@girishramnani
Copy link
Contributor Author

The older images are not removed/deprecated. I check it but also verified by this comment openshift/openshift-docs#19597 (comment)

@lholmquist
Copy link

Also see this comment: openshift/openshift-docs#19597 (comment)

nodejs-8-rhel7 as well as both versions of rhoar-nodejs are no longer supported. While OpenShift does not update imagestreams in stable branches, that does not mean we should encourage further use of unsupported versions.

@girishramnani girishramnani added this to For consideration in Sprint 181 via automation Mar 9, 2020
@girishramnani girishramnani removed this from To do in Sprint 180 Mar 9, 2020
@girishramnani girishramnani moved this from For consideration to To do in Sprint 181 Mar 9, 2020
@girishramnani girishramnani added the status/blocked Denotes an issue or PR that is blocked on something (e.g., issue/PR in different repo) label Mar 11, 2020
@girishramnani
Copy link
Contributor Author

we need to resolve these issues https://github.com/openshift/odo/issues?q=is%3Aissue+is%3Aopen+label%3Anext-oc-version before we could add nodejs:12 as supported image

@girishramnani girishramnani added triage/ready and removed status/blocked Denotes an issue or PR that is blocked on something (e.g., issue/PR in different repo) triage/needs-information Indicates an issue needs more information in order to work on it. labels Mar 11, 2020
@kadel
Copy link
Member

kadel commented Mar 18, 2020

we need to resolve these issues https://github.com/openshift/odo/issues?q=is%3Aissue+is%3Aopen+label%3Anext-oc-version before we could add nodejs:12 as supported image

no, we need to resolve this first! Some of the issues will go away when nodejs images are marked as supported.

We need to add nodejs images into supported images and test what issues will be fixed!

@girishramnani girishramnani moved this from To do to In progress in Sprint 181 Mar 19, 2020
@girishramnani girishramnani moved this from In progress to For review in Sprint 181 Mar 19, 2020
@girishramnani girishramnani added this to For consideration in Sprint 182 via automation Mar 30, 2020
@girishramnani girishramnani removed this from For review in Sprint 181 Mar 30, 2020
@girishramnani girishramnani moved this from For consideration to For review in Sprint 182 Mar 30, 2020
Sprint 182 automation moved this from For review to Done Apr 6, 2020
@rm3l rm3l added the v2 Issue or PR that applies to the v2 of odo label Jun 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/user-story An issue of user-story kind priority/High Important issue; should be worked on before any other issues (except priority/Critical issue(s)). v2 Issue or PR that applies to the v2 of odo
Projects
Archived in project
Sprint 182
  
Done
Development

Successfully merging a pull request may close this issue.

5 participants