che icon indicating copy to clipboard operation
che copied to clipboard

Is it possible to install/run eclipse-che on rke2?

Open ronaldor1968 opened this issue 1 year ago • 2 comments

Summary

I have a home cluster with 3 physical machines, an rke2 with a master and 3 agents (counting the one installed on the master), is it possible to install eclipse-che? Or do I need k8s? Any prerequisites that rke2 does not provide since it is a lighter implementation.

Relevant information

No response

ronaldor1968 avatar Nov 21 '24 16:11 ronaldor1968

@ronaldor1968 hello, thank you for your interest in the project. Basically, it should be very well possible to install Eclipse Che on Rancher - https://eclipse.dev/che/docs/stable/administration-guide/supported-platforms/

However, we currently do not have official documentation for this provider. It would be great if the Community would kick in and contribute relevant docs to https://eclipse.dev/che/docs/stable/administration-guide/installing-che/ smth. similar to contibution for EKS that is under review now - https://github.com/eclipse-che/che-docs/pull/2808

Some articles that might be useful for this context:

  • https://eclipse.dev/che/docs/stable/administration-guide/installing-che-on-microsoft-azure/
  • https://che.eclipseprojects.io/2022/07/25/@karatkep-installing-eclipse-che-on-aks.html
  • https://eclipse.dev/che/docs/stable/administration-guide/installing-che-on-the-virtual-kubernetes-cluster/

ibuziuk avatar Nov 22 '24 12:11 ibuziuk

I had already read the documentation, and I also have this idea that it is possible, my doubt starts at step 26 of the documentation for the installation in a kubernet cluster, where in chectl the platform is directly specified, k8s (chectl server:deploy
--platform k8s
--domain $DOMAIN_NAME
--che-operator-cr-patch-yaml /tmp/che-patch.yaml), being in doubt if I could try to follow the documentation or if we still have some specific issues that need detailing.

Thank you for the clarification.

ronaldor1968 avatar Nov 22 '24 18:11 ronaldor1968

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 avatar Nov 13 '25 01:11 che-bot