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

Spike: PoC for single-host/default-host mode for Che Theia #14002

Closed
skabashnyuk opened this issue Jul 24, 2019 · 3 comments
Closed

Spike: PoC for single-host/default-host mode for Che Theia #14002

skabashnyuk opened this issue Jul 24, 2019 · 3 comments
Assignees
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.
Milestone

Comments

@skabashnyuk
Copy link
Contributor

Is your task related to a problem? Please describe.

The goal of the task is a technical study of #12971 (comment) problem. If that possible provide some variants of Poc how to solved. To narrow the scope at this moment we can concentrate only on Che Theia and devfiles from https://github.com/eclipse/che-devfile-registry

Describe the solution you'd like

single-host/default-host mode for Che Theia is working

Describe alternatives you've considered

n/a

Additional context

#12971

@skabashnyuk skabashnyuk added kind/task Internal things, technical debt, and to-do tasks to be performed. team/platform severity/P1 Has a major impact to usage or development of the system. labels Jul 24, 2019
@slemeur slemeur changed the title Spark: PoC for single-host/default-host mode for Che Theia Spike: PoC for single-host/default-host mode for Che Theia Jul 24, 2019
@slemeur slemeur added this to the 7.1.0 milestone Jul 24, 2019
@slemeur
Copy link
Contributor

slemeur commented Jul 24, 2019

cc @akervern

@metlos
Copy link
Contributor

metlos commented Aug 6, 2019

So I've made some initial progress into making this working again. I've started with single-user mode and have found that the original way this was developed only works with nginx-ingress-controller in version 0.21.0 or older (present in minkube <= 0.35.0). There was an incompatible change in version 0.22.0 (in minikube 1.0.0 or newer) that breaks our approach and we need to modify the way we define the ingress controller related annotations as well as how we define the paths handled by the ingresses. Please refer to the PR #14134 where the progress is being reported and tracked.

Note that the nginx-ingress-controller is currently on version 0.25.0.

Also note that I am not aware of this being tested or made working with any other ingress controller. If such tests have been performed, could you please point me to the results, @eclipse/eclipse-che-qa?

@metlos
Copy link
Contributor

metlos commented Aug 14, 2019

I've created issue #14229 to track testing on different cloud platforms. I've also created #14189 to track the support of single/default-host strategy on multi-user.

As such, I think this spike issue can be closed.

@metlos metlos closed this as completed Aug 14, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

3 participants