As discovered in CRW-1422, the way the async-storage-server and -sidecar images are used with Che 7 is via a hardcoded image w tag reference in che.properties (not airgap-compatible) and via a plugin in the plugin registry (potentially airgap-compatible, but using old workspace provisioning model).

Since we've decided there's no need to implement async storage for Che 7, this becomes a new feature to be included along with devworkspace engine support in CRW 2.15+.

But with DW, the images are hardcoded references in the DW CSV, making it impossible to provide them in CRW; instead they need to be part of the DW payload.

So, the current productized images are here:

• http://pkgs.devel.redhat.com/cgit/containers/codeready-workspaces-async-storage-server/tree/?h=crw-2.14-rhel-8
• http://pkgs.devel.redhat.com/cgit/containers/codeready-workspaces-async-storage-sidecar/tree/?h=crw-2.14-rhel-8

Midstream code is here, transformed from upstream:

• https://github.com/redhat-developer/codeready-workspaces-images/tree/crw-2.14-rhel-8/codeready-workspaces-async-storage-server
• https://github.com/redhat-developer/codeready-workspaces-images/tree/crw-2.14-rhel-8/codeready-workspaces-async-storage-sidecar

We'll need to follow a modified approach per the image productization guide so that we can include these images in the http://pkgs.devel.redhat.com/cgit/?q=devworkspace container set.

Need to determine how to do this along with cpass/honeybadger integration, and how much of this effort will fall on Prod/CRW team vs. Controller/DW team.