Detect + avoid problems with us.icr.io registry namespace collisions

[kipharris]

As I understand it, when installing onto the OCP service on IBM Cloud:

The installation terraform uses the resource group name that is specified in settings/environment.tfvars, as the value of the namespace to be created in the multi-tenant registry at us.icr.io. There are two problems with this strategy, which both impact the consumability of the asset.

1.) Since the registry in this scenario is multi-tenant, the namespace (== the resource group name) must be unique within the region. I do not see guidance in our docs of how to verify that the Admin/Dev can verify that a selected resource group name / namespace value is unique. Also, In fact, I could not find any guidance abount resource group name constraints when I searched just now.

2.) If the naive user simply uses the "default" resource group for his install, the install will break (i did this 1st time thru, but didn't record the error).

In both cases, the errors leave at least a few resources laying around which are a little trouble to clean up. The root cause of the failed install may or may not be apparent to the user.

Can the automation be augmented, so that it creates and verifies the needed unique name, without having to educate the user on this obsure point?

Thanks.