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.

Sign up for GitHub

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

Jump to bottom

Need to test the airgap deployment against OpenShift 4.2 restricted networks #15079

Closed
ibuziuk opened this issue Nov 4, 2019 · 2 comments
Closed

Need to test the airgap deployment against OpenShift 4.2 restricted networks #15079

ibuziuk opened this issue Nov 4, 2019 · 2 comments
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.
Milestone
7.5.0

Comments

@ibuziuk
Copy link
Member

ibuziuk commented Nov 4, 2019 •
edited
Loading

Is your task related to a problem? Please describe.

Need to test the airgap deployment against OpenShift 4.2 restricted networks - https://docs.openshift.com/container-platform/4.2/operators/olm-restricted-networks.html

Documentation for airgap deployment - eclipse-che/che-docs#868

Follow up email:

Most operator container images use tags. Our documented process for mirroring operator images in a disconnected environment will only work for images that use digests and NOT tags.
https://docs.openshift.com/container-platform/4.2/operators/olm-restricted-networks.html
So, if your operator uses tag image references instead of digests (90% of all operators use tags in their container images) then they will not successfully mirror following our disconnected instructions.
I don't yet know if this restriction will apply to the operand images as well. But I wouldn't be surprised if it does.
@ibuziuk ibuziuk added the kind/task Internal things, technical debt, and to-do tasks to be performed. label Nov 4, 2019
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Nov 4, 2019
@ibuziuk ibuziuk added team/osio severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Nov 4, 2019
@ibuziuk ibuziuk modified the milestones: Backlog - Hosted Che, 7.5.0 Nov 4, 2019
@nickboldt
Copy link
Contributor

Aren't we making a distinction between "disconnected environment" (offline) and "restricted environment" (air gap) ?

The former is not supported in CRW 2 (yet). The latter should work (with some setup required, eg., prepulling container images to an internal registry).

@ibuziuk
Copy link
Member Author

ibuziuk commented Nov 27, 2019

Done and demo is shown during the sprint review

@ibuziuk ibuziuk closed this as completed Nov 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Milestone
7.5.0
Development

No branches or pull requests
3 participants
@nickboldt @ibuziuk @che-bot