che: Some devfiles are not compatible with Hosted Che (che.openshift.io) due to 3 GB quota limitations

Current Hosted Che “Terms of service” allows using only 3GB of RAM for workspace. At the same time some of the devfiles from the registry like java-web-spring are failing with the quota issue:

NOTE: event though globalMemoryLimit: 2674Mi is set in the meta.yaml, I suspect it does not take into account the jwt-proxy pod

We need to:

identify the list of problematic devfiles that would fail with the quota issue https://github.com/eclipse/che/issues/13969#issuecomment-514207340
try to update defviles to make them compatible with Hosted Che resources (if not possible need to decide if those devfiles should be in the registry )
- apache-camel-springboot https://github.com/eclipse/che-devfile-registry/pull/46
- java-mysql https://github.com/eclipse/che-devfile-registry/pull/61
- java-web-spring https://github.com/eclipse/che-devfile-registry/pull/62

[1] https://www.eclipse.org/che/docs/che-7/hosted-che.html#terms-of-service_{context}

About this issue

Original URL
State: closed
Created 5 years ago
Comments: 15 (15 by maintainers)

Most upvoted comments

[23.07.2019] Check for worksapce startup quotes with the latest version of devfile registry at prod-preview:

✓ angular
✘ apache-camel-springboot [Should be fixed by PR ~~and Follow-up~~]
✓ dotnet
✓ golang
✓ java-gradle
✓ java-maven
✘ java-mysql [Should be fixed by PR]
✘ java-web-spring [Should be fixed by PR]
✓ java-web-vertx
✓ nodejs-mongo
✓ nodejs-react
✓ nodejs
✓ php-laravel
✓ php-mysql
✓ php-symfony
✓ php-web-simple
✓ python-django
✓ python

ScrewTSW on Jul 29, 2019

@apupier if it works we would merge it and make available 😉

my last manual tests on preprod are working https://github.com/eclipse/che-devfile-registry/pull/46#issuecomment-514515189

apupier on Jul 24, 2019

I mean if we cannot reduce the amount of memory we can remove the devfiles from the openshift.io registry.

for Apache Camel stack, we can reduce the memory, see https://github.com/eclipse/che-devfile-registry/pull/46 and https://github.com/eclipse/che/issues/13832

so nto having Apache Camel stack on che.openshift.io is not blocker? an alternate solution if there is a different registry to use is to set back the working memory values only in the rh-che repository?

apupier on Jul 24, 2019