Skip to content
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

Closed
Tracked by #20830
amisevsk opened this issue Nov 2, 2021 · 8 comments
Closed
Tracked by #20830

Check that DWO is compatible with network-isolated clusters #668

amisevsk opened this issue Nov 2, 2021 · 8 comments
Assignees
Labels
sprint/current Is assigned to issues which are planned to work on in the current team sprint
Milestone

Comments

@amisevsk
Copy link
Collaborator

amisevsk commented Nov 2, 2021

Description

We need to make sure that DWO functions correctly in an airgapped cluster and document any issues or additional requirements that are needed.

@ibuziuk ibuziuk added sprint/current Is assigned to issues which are planned to work on in the current team sprint and removed sprint/next labels Nov 10, 2021
@max-cx
Copy link

max-cx commented Nov 15, 2021

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?

@ibuziuk
Copy link
Contributor

ibuziuk commented Nov 19, 2021

@ibuziuk
Copy link
Contributor

ibuziuk commented Dec 2, 2021

@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

@dmytro-ndp
Copy link
Contributor

dmytro-ndp commented Dec 9, 2021

@ibuziuk
Copy link
Contributor

ibuziuk commented Jan 12, 2022

standalone DWO has been checked against airgap cluster.
Now we need to verify Eclipse Che 7.42.0 with the DevWorkspace enabled on the same environment

@l0rd
Copy link
Collaborator

l0rd commented Feb 20, 2022

Closing as this should have been verified now

@l0rd l0rd closed this as completed Feb 20, 2022
@ibuziuk ibuziuk reopened this Feb 22, 2022
@ibuziuk
Copy link
Contributor

ibuziuk commented Feb 22, 2022

@ScrewTSW @musienko-maxim @dmytro-ndp folks, reopening this issue for clarification.
I'm not sure if this flow has been verified e2e with the recent fixes on the operator side.

@ibuziuk
Copy link
Contributor

ibuziuk commented Feb 22, 2022

Closing this issue after discussion and opening eclipse-che/che#21205 for e2e latest Eclipse Che verification in the air-gap mode.

@ibuziuk ibuziuk closed this as completed Feb 22, 2022
@amisevsk amisevsk added this to the v0.13.0 milestone Feb 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sprint/current Is assigned to issues which are planned to work on in the current team sprint
Projects
None yet
Development

No branches or pull requests

6 participants