Need the design change to configure custom domains in DataPower on ICP at the helm chart installation

As the current design, it is not recommended that we configure custom domains in DataPower on ICP because we can't customize the helm chart for DataPower freely. Currently, "Gateway Extension" is the one of alternative solutions, which means that some artifacts in custom domains are injected into APIM domain by any commands in API Toolkit. However, we can't accept this current behavior because of following reasons;

1) The installation for API Toolkit is mandatory, but we have some some customers who don't use API Toolkit at all. In this case, they can't agree the solution in "Gateway Extension".

2) A lot of customers have already configured custom domains in DataPower, tied with API Connect (on-premises). If this design is not improved, it will have heavy impacts on well-experienced customers who have a plan to update API Connect on ICP because of below 3).

3) Some artifacts in custom domains will be exported in trying to use "Gateway Extension", but eventually, they must be still maintained in custom domain. Currently, we can set up custom domains, but they are not persisted, so all the artifacts in custom domains will be deleted once custom domains are re-started. It means that we can't have any stable envs where artifacts in custom domains are maintained.

Based on the above, we have strongly requested that we can set up custom domains in DataPower on ICP as in the past and they are also persisted. The current design will really be blocking or be shrinking our future possible business opportunities for API Connect on ICP.