[docs] Documentation for overriding all the involved images for the airgap scenario

[nickboldt]

Is your enhancement related to a problem? Please describe.

As noted in #13886 we can override many of the Che images at deploy time via a custom resource yaml.

• cheImage
• postgresImage
• identityProviderImage
• pvcJobsImage
• devfileRegistryImage
• pluginRegistryImage

But this does not include ALL the images. The following are missing:

• Che Theia image
• Che plugin broker image
• Che JWT proxy
• Che Theia endpoint runtime image
• Che remote plugins (eg., openshift connector, kubernetes tooling, java8, java11)

Describe the solution you'd like

Add more fields to the CR, and have those supported when using chectl to deploy Che.

Additional context

This is in support of offline/airgap scenarios, where we can't just pull random container images from quay/rhcc, but need to set specific ones within an organization (or specific productized ones).

See also

• https://issues.jboss.org/browse/CRW-318
• https://issues.jboss.org/browse/CRW-240

[davidfestal]

In a number of cases, I assume that for now you can change them by simply adding the corresponding environment variable in the custom config map.
I did it just today for the plugin-broker docker image.
But sure, this is not integrated with chectl, and is not really easy to use

[slemeur]

Installations that is concerned by this issue are: from chectl and from operatorhub

[ibuziuk]

@nickboldt please clarify why it is P1, moved to 7.x atm

[nickboldt]

Need this for offline / airgap, so P1/blocker.

But sure, this is not integrated with chectl, and is not really easy to use

If we can't do full integration then at least a blog/doc with example would suffice for a first pass. But we need SOMETHING here for customers.

[davidfestal]

After issue #13886 (comment) is fixed, this issue should mainly consist in providing some scenario-oriented documentation, dedicated to the offline / airgap mode.
Do you agree @nickboldt ?

[nickboldt]

Yes, that would be great for Che 7 and would work as the baseline from which to create CRW 2 docs too.

Related downstream issues:

• https://issues.jboss.org/browse/CRW-303 migration 1.2 -> 2.0
• https://issues.jboss.org/browse/CRW-240 offline scenarios

[nickboldt]

Related issues:

• Allow overriding of all images used in Che deployment when using operator #14216 - Add missing che properties for images that are not configurable yet
• Replace the use of custom operator config map with a map inside the custom resource. #14635 - Make every che property configurable through the operator CR
• Operator airgap mode support #14734 - New CR AirGap attributes that allow to overrides images

And these older ones:

• chectl: --devfile-registry-url and --che-operator-cr-yaml do not play well together #14589 - chectl: --devfile-registry-url and --che-operator-cr-yaml does not play well together
• chectl server:start does not expose all images for override #14186 - chectl server:start does not expose all images for override

[ibuziuk]

@nickboldt I'm going to close this one in favor of #14866
Are you ok with that ?

[nickboldt]

Sure. 3 of the 5 related issues on this one are resolved too -- it's just the chectl issues that remain unresolved.