Since the increased disk space from 2.15 -> 2.16 is only a few MBs overall (from 2M to 20M), and it's just more sample code that customers can try, I'm not too worried about this new feature-not-a-bug (see CRW-2500).

However, it would be good to follow up in https://github.com/devfile/devworkspace-operator/issues/757 for performance reasons (needless disk usage / faster workspace startup).

Some options we could explore include:

• delete unneeded content from the crw-samples forks so there's less to clone
• add v2 attributes (to match what's in the v1 devfiles), and parse those when building the arigapped registry, eg.,

  attributes:
    che-devfile-registry.eclipse.org/sparse-checkout: kitchensink-jsp