-
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
Che 6 on OpenShift - Phase 1 #7321
Comments
@slemeur |
The same for compose |
@slemeur As for me, it looks like most of these points are not covered on Che5. Can you elaborate on why they should be requirements for Che6? |
@garagatyi : It's not because it is not in Che 5 openshift connector that we should not do it in Che 6. You maybe have in mind only the requirements for Che 6 to run on OSIO - but keep in mind that all codenvy customers are waiting for a migration path from Codenvy to Che 6 on Openshift (codenvy/codenvy#2517). For those who were using Che on Docker in the past and willing to use an OpenShift based infrastructure, the support of the different recipe types is important. |
@slemeur I see. I definitely thought about OSIO use-case, not the most common one. Thank you for the explanation |
@slemeur can you elaborate a bit more on " Docs: on user's permissions on files/folders to be defined in OS" what do you mean? |
When discussing with @eivantsov , it sounds that there could be limitation applied to the file system which would prevent Che to behaves properly. |
@slemeur can you confirm that this epic is complete and we can close it? |
Done ! |
The goal of this epic is to track the readiness of Che 6 on OpenShift (OCP, OSD and minishift).
OpenShift SPI Implementation
Packaging
Requirements on workspace runtimes
Multi-user and Multi-tenancy
Adapted Features and Capabilities
oc rsh
?) / Docs and maybe update to SSH button in workspace update ssh button on IDE for Openshift #7664Configuration and Requirements
sudo
accessAdministration
Linked Issues
codenvy/codenvy#2517
The text was updated successfully, but these errors were encountered: