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

Installing Che in a restricted environment on OpenShift #21393

Closed
Tracked by #21395 ...
themr0c opened this issue May 12, 2022 · 3 comments
Closed
Tracked by #21395 ...

Installing Che in a restricted environment on OpenShift #21393

themr0c opened this issue May 12, 2022 · 3 comments
Assignees
Labels
area/doc Issues related to documentation area/install Issues related to installation, including offline/air gap and initial setup kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.
Milestone

Comments

@themr0c
Copy link
Contributor

themr0c commented May 12, 2022

Describe the bug

The script in https://www.eclipse.org/che/docs/stable/administration-guide/installing-che-in-a-restricted-environment/ is not entirely functional:

  • The custom catalog source, once deployed, stays in TRANSIENT_FAILURE status.

  • The mirroring has errors putting the images into the expected destination.

Che version

7.46

Steps to reproduce

Expected behavior

  • The restricted-environment-install catalog source status is not TRANSIENT_FAILURE
  • No errors during mirroring

Runtime

CodeReady Container

Screenshots

Screenshot from 2022-05-11 15-57-06

Screenshot from 2022-05-11 18-05-50

Installation method

other (please specify in additional context)

Environment

Linux

Eclipse Che Logs

No response

Additional context

Followup on eclipse-che/che-docs#2307 and #21284

@themr0c themr0c added the kind/bug Outline of a bug - must adhere to the bug report template. label May 12, 2022
@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 May 12, 2022
@themr0c themr0c added severity/P1 Has a major impact to usage or development of the system. area/doc Issues related to documentation area/install Issues related to installation, including offline/air gap and initial setup labels May 12, 2022
@themr0c themr0c added this to the 7.46 milestone May 12, 2022
@themr0c themr0c self-assigned this May 12, 2022
@nickboldt nickboldt removed the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label May 12, 2022
@ibuziuk ibuziuk mentioned this issue May 12, 2022
58 tasks
@tolusha tolusha mentioned this issue May 13, 2022
49 tasks
@tolusha tolusha mentioned this issue Jun 3, 2022
64 tasks
@nickboldt
Copy link
Contributor

nickboldt commented Jun 6, 2022

Downstream version in https://red-hat-developers-documentation.pages.redhat.com/red-hat-devtools/devspaces/asciidoctor/administration-guide/#installing-devspaces-in-a-restricted-environment-on-openshift looks like this -- same script, different parameters:

$ bash prepare-restricted-environment.sh \
  --ocp_ver "4.10" \
  --devworkspace_operator_index "registry.redhat.io/redhat/redhat-operator-index:v4.10" \
  --devworkspace_operator_version "v0.14.1" \
  --prod_operator_index "registry.redhat.io/redhat/redhat-operator-index:v4.10" \
  --prod_operator_package_name "devspaces-operator" \
  --prod_operator_version "v3.0.0" \
  --my_registry "<my_registry>"

@themr0c
Copy link
Contributor Author

themr0c commented Jun 15, 2022

Now we have something running.
The mistake was: filter out the old bundles but not the packages list.
But it's still not optimal: we should filter the packages and bundles to have a smaller number of related images to mirror.
See: https://github.com/eclipse-che/che-docs/blob/main/modules/administration-guide/attachments/restricted-environment/prepare-restricted-environment.sh#L46

NOTE: Test on a real cluster with a real external registry. Don't use the internal CRC registry.

@themr0c
Copy link
Contributor Author

themr0c commented Jun 15, 2022

I believe it would make sense to have this feature in chectl rather than in a script in the documentation repository.

@themr0c themr0c closed this as completed Jun 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/doc Issues related to documentation area/install Issues related to installation, including offline/air gap and initial setup kind/bug Outline of a bug - must adhere to the bug report template. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

4 participants