-
Notifications
You must be signed in to change notification settings - Fork 56
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
Check that DWO is compatible with network-isolated clusters #668
Comments
Hi, a question to the assignee of this issue: Will the outcome require any changes to the relevant content of the Installation Guide or Administration Guide or End-user Guide? Yes/No? |
issues related to this spike: |
@rhopp @dmytro-ndp folks, could you please point to the instructions that QA are using for the air-gap / network-isolated clusters setup? The plan is that @ScrewTSW is going to own the verification of the DevWorkspace running in this environment |
@ibuziuk: there is a set of scripts created by Radim and Flavius, which we are using downstream to setup OCP for CRW testing:
Here the document prepared by Flavius: https://docs.google.com/document/d/1ZbzhoUYhV7gbZVJkX5o0kId8VOw1TNuWso89PNAP8uw/edit?usp=sharing |
standalone DWO has been checked against airgap cluster. |
Closing as this should have been verified now |
@ScrewTSW @musienko-maxim @dmytro-ndp folks, reopening this issue for clarification. |
Closing this issue after discussion and opening eclipse-che/che#21205 for e2e latest Eclipse Che verification in the air-gap mode. |
Description
We need to make sure that DWO functions correctly in an airgapped cluster and document any issues or additional requirements that are needed.
The text was updated successfully, but these errors were encountered: