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

Test single-host/default-host workspace strategy on multi-user mode on different cloud platforms #14230

Closed
metlos opened this issue Aug 14, 2019 · 1 comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@metlos
Copy link
Contributor

metlos commented Aug 14, 2019

All our primary development of Che server happens on minikube/minishift, which is not what is put in production.

Different cloud providers realize ingresses using different kinds of ingress controllers within those clusters.

We should therefore test that we can successfully use Che in such clusters.

Multi-user mode is going to be common scenario for Che server deployment in a cluster so we should make sure that we are able to configure Che in such a way that it works in "real" clusters.

The list of tested platforms should IMHO at least include:

  • AWS
  • GKE

More importantly though, we should try to use other ingress controllers than just nginx in those clusters and try to make Che server correctly work in single-host mode using those other ingress controllers.

The single-host strategy in multi-user mode is tracked by the issue:
#14189

@metlos metlos added the kind/task Internal things, technical debt, and to-do tasks to be performed. label Aug 14, 2019
@slemeur slemeur added this to the 7.2.0 milestone Aug 14, 2019
@gazarenkov gazarenkov removed this from the 7.2.0 milestone Oct 2, 2019
@che-bot
Copy link
Contributor

che-bot commented Apr 1, 2020

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 1, 2020
@che-bot che-bot closed this as completed Apr 8, 2020
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. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants