-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Docs: Installation to On Prem Restricted Kubernetes Environment is Missing #21646
Comments
I also would be really interested for an up to date documentation :) |
Hello, Eclipse Che is installable on all major Public Clouds e.g. AKS / GCP however we do not have the docs in place since setting up Users' Authentication is required for deploying Che on Kubernetes infrastructures which can vary (for OpenShift Container Platform no additional setup is needed) Contributions from the Community are most welcome for other cloud providers as blog posts or official docs Regarding the Restricted Environments installation, we have official docs for OpenShift - https://www.eclipse.org/che/docs/next/administration-guide/installing-che-in-a-restricted-environment/ the process should be similar for other providers, where images are mirrored to the cluster registry before the installation. |
Issues go stale after Mark the issue as fresh with If this issue is safe to close now please do so. Moderators: Add |
Community contribution is most welcome - adding |
Summary
Documentation page of stable version does not offer a well documented installation tutorial to run Eclipse Che on on-prem restricted K8S environment. There is one documentation page for v.7.41 - [https://www.eclipse.org/che/docs/che-7/installation-guide/installing-che-in-a-restricted-environment/] - but I guess it is removed for the stable one.
My aim is to install Eclipse Che on our on-prem VMWare Tanzu Kubernetes Grid environment. I would be really thankful if a detailed documentation will be provided for those who do not use public cloud vendors.
Relevant information
No response
The text was updated successfully, but these errors were encountered: