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

Needed images to deploy Eclipse Che in disconnected environment #20539

Closed
michelecurioni opened this issue Sep 24, 2021 · 7 comments
Closed

Needed images to deploy Eclipse Che in disconnected environment #20539

michelecurioni opened this issue Sep 24, 2021 · 7 comments
Labels
area/install Issues related to installation, including offline/air gap and initial setup kind/question Questions that haven't been identified as being feature requests or bugs. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P2 Has a minor but important impact to the usage or development of the system.

Comments

@michelecurioni
Copy link

Summary

Hi all,
we would like to run eclipse che in an airgapped environment, but it's not clear what images need to be available in the local registry for the operator to function.
Is there a way to get a list of all the images for a specific version of the operator?
Also, it would be useful to call out any platform dependencies for a specific version.
This page talks about 7.36.x (https://www.eclipse.org/che/docs/che-7/installation-guide/supported-platforms/), is there a way to get similar information from the operator release notes.

Thanks,
Michele

Relevant information

No response

@michelecurioni michelecurioni added the kind/question Questions that haven't been identified as being feature requests or bugs. label Sep 24, 2021
@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 Sep 24, 2021
@tolusha
Copy link
Contributor

tolusha commented Sep 27, 2021

Hi @michelecurioni
The list of images does not depend on the specific platform.
We have a doc [1] and script [2] to test Eclipse Che operator in a restricted environment.

[1] https://www.eclipse.org/che/docs/che-7/installation-guide/installing-che-in-a-restricted-environment/
[2] https://github.com/eclipse-che/che-operator/blob/main/.ci/oci-disconnected.sh

@tolusha tolusha added the area/install Issues related to installation, including offline/air gap and initial setup label Sep 27, 2021
@michelecurioni
Copy link
Author

Hi @tolusha,
I looked at [1], and I can see a list of required images here: https://www.eclipse.org/che/docs/che-7/installation-guide/installing-che-in-a-restricted-environment/#preparing-a-private-registry_che, but that list doesn't specify which version of those images need to be downloaded. I imagine a specific version of the operator will require specific version of those images.
Are those the only ones required for a successful installation?
It would be useful to have a way to list exactly what images the operator will need otherwise when deployed to the airgapped environment it will fail.

Thanks,
Michele

@tolusha
Copy link
Contributor

tolusha commented Sep 27, 2021

That's a good question. It seems the doc is not full.
So, the complete list of images and their tags can be extracted from che-operator deployment + you need the operator image itself [1]

[1] https://github.com/eclipse-che/che-operator/blob/7.36.2/config/manager/manager.yaml#L60-L95

@michelecurioni
Copy link
Author

That's what I was looking for, thanks.
Could you create a feature request to expose that list via command or store it in a file?
It's a bit hidden away, and I'd like to automate the download of everything required by the operator so that I can transfer it all to the airgapped environment in one archive.

There are also other images referred to in that yaml, like RELATED_IMAGE_che_plugin_sidecar_plugin_registry_image_...
Are those optional?
How do I know which ones are optional, and which ones are required?

Thanks,
Michele

@dkwon17 dkwon17 removed the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Sep 27, 2021
@tolusha tolusha changed the title che operator dependencies Images needed to deploy Eclipse Che in disconnected environment Sep 28, 2021
@tolusha tolusha changed the title Images needed to deploy Eclipse Che in disconnected environment Needed images to deploy Eclipse Che in disconnected environment Sep 28, 2021
@tolusha
Copy link
Contributor

tolusha commented Sep 28, 2021

Regarding plugin & devfile registries images. You don't need to mirror them all but the only ones needed for your case.

  1. build offline plugin & devfile registries following the doc [1]
  2. check all external images
    docker run -ti <DEVFILE_REGISTRY_IMAGE> cat /usr/local/apache2/htdocs/devfiles/external_images.txt
    docker run -ti <PLUGIN_REGISTRY_IMAGE> cat /usr/local/apache2/htdocs/v3/external_images.txt
  3. Mirror ones for you devfile & plugins

[1] https://www.eclipse.org/che/docs/che-7/installation-guide/installing-che-in-a-restricted-environment/

@tolusha tolusha added sprint/next severity/P2 Has a minor but important impact to the usage or development of the system. team/deploy labels Oct 15, 2021
@tolusha tolusha mentioned this issue Oct 18, 2021
25 tasks
@tolusha tolusha added this to the 7.39 milestone Oct 20, 2021
@tolusha tolusha mentioned this issue Nov 9, 2021
27 tasks
@tolusha tolusha modified the milestones: 7.39, 7.40 Nov 9, 2021
@tolusha tolusha mentioned this issue Nov 29, 2021
28 tasks
@tolusha tolusha removed this from the 7.40 milestone Dec 1, 2021
@che-bot
Copy link
Contributor

che-bot commented May 30, 2022

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 30, 2022
@tolusha tolusha added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 30, 2022
@tolusha
Copy link
Contributor

tolusha commented Sep 19, 2024

Closed in favor of #21646

@tolusha tolusha closed this as completed Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/install Issues related to installation, including offline/air gap and initial setup kind/question Questions that haven't been identified as being feature requests or bugs. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P2 Has a minor but important impact to the usage or development of the system.
Projects
None yet
Development

No branches or pull requests

4 participants