However, this is just a temporary solution. Long term we need to be able to support the specialized installation method that is described in the same link (This is where we originally started). It is a very real scenario that OpenShift admins will want to have deployed resources in different namespaces. We will need to be able to support the specialized configuration, and I've created a separate tech debt issue to bring it back here: https://github.com/cloud-native-toolkit/software-everywhere/issues/191
To get CP4D & DB2 modules delivered, switch to the express installation pattern, as defined here (everything in one namespace): https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=installing
However, this is just a temporary solution. Long term we need to be able to support the specialized installation method that is described in the same link (This is where we originally started). It is a very real scenario that OpenShift admins will want to have deployed resources in different namespaces. We will need to be able to support the specialized configuration, and I've created a separate tech debt issue to bring it back here: https://github.com/cloud-native-toolkit/software-everywhere/issues/191