A new CI release (TBC) job (based on the iso-no-registry workflow) must be defined to run the specific feature tests. They should be visible in https://sippy.dptools.openshift.org/sippy-ng/tests/4.22/details?filters=%7B%22items%22%3A%[…]3A%22FeatureGate%3ANoRegistryClusterInstall%22%7D%5D%7D.

The deployed cluster must be in TechPreview. Reason: a goal of the task is not only to demonstrate that the feature is behaving as expected, but also that it does not break other TP features (conversely, running our feature in a TP preview cluster may not work due other TP features - such as the SigStore one; in such case add necessary Jira cards to fix the problem)

Optional: run also the openshift/conformance/parallel suite

Default ocp e2e test step: https://github.com/openshift/release/blob/master/ci-operator/step-registry/openshift/e2e/test/openshift-e2e-test-commands.sh

Compare these tests with baremetalds e2e