Allow server:start to deploy a new Che even if one is already running

[che-bot]

From chectl created by AndrienkoAleksandr: che-incubator/chectl#32

It would be nice to have ability set up helm application name. It should resolve conflict in case if user want to have few CHE servers on the one Minikube. For example I used Minikube with already installed CHE. I used chectl server:start and I expected that chectl tool will create for me separated new che and I will get two CHE servers. But I've got conflict because, chectl tried to use resources from my first already installed Eclipse CHE in the another namespace, because helm application name was the same.

[che-bot]

Looks good for me.

[che-bot]

@AndrienkoAleksandr your scenario makes sense but I would like to avoid the flag to be helm specific because the problem here is more generic:

what server:start should do if a Che instance is already deployed: update it, create a new one or fail?

It currently updates it (with helm update) but I think a better approach would be to use a flag --if-already-exist that accepts 3 values:

• fail (the default)
• update (that calls chectl server:update)
• new-instance

What do you think?

[che-bot]

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.

[tolusha]

Fixed by che-incubator/chectl@2fca137

We allows to deploy several Eclipse Che on a single cluster using --installer operator.
Every deployment will have it's own clusterrole and clusterrolebinding objects.
Besides this we check if CRD object is the same and throws an error if not.