-
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] Document airgap/offline Che deployment process/options #14866
Comments
How does this issue relate to the following: #14088 (comment) ? Maybe it should replace it ? @l0rd @nickboldt wdyt ? |
There are two types of doc required here: a) how do I build an airgap-compliant image? Part (a) is about which flags to pass to I can see this doc being useful for Che 7 extenders wanting to build custom registries to add/remove new plugins/devfiles. Or for CRW 2 airgap customers wishing the same thing - custom registries with more/less content than the OOTB default Part (b) is... now that I have a build, how do I tell This is also for Che 7 extenders but could also be useful for a CRW 2 customer who just wants to deploy the CRW 2 OOTB experience (non-customized registries) inside an airgap environment. So it's either two documents or one two-part document. Given you might only need the second doc if you're not looking to customize registry content, I might suggest it's better as two docs. |
Draft document: https://gist.github.com/amisevsk/c98a48bba01f3fa72d7ab7dfea45fc36 There are a few known issues and still some work required in filling in various options (e.g. how to deploy using chectl). |
PR merged. |
Is your task related to a problem? Please describe.
Issues #14733, #14733, eclipse-che/che-plugin-registry#211, and eclipse-che/che-plugin-broker#70 add offline functionality to Che registries and workspaces. This functionality is going to be supported by the operator (#14734) and by chectl (#14699)
We should add a new section to the Che documentation on how to use these options and how to deploy Che in an airgap environment.
The text was updated successfully, but these errors were encountered: