Setup SaaS multi-tenancy (instance) MEAN app with Kubernetes

We're a startup company busy realising a Multi-Tenancy SaaS platform written in MEAN stack and uses Kubernetes and Docker for Container orchestration. We need help to write a Kubernetes API in Nodejs that will start a separate instance of the app in it's own namespace upon Customer signup. Help me understand the workings of Kubernetes in this context. The app is currently setup with the following structure: Customer Namespace: ([login to view URL]) - Customer Frontend (Angular 8): Includes landing page of the platform and links to customer sign up and user login in. - Customer API (NodeJS loopback): Endpoints for Customers and specifically customer sign up that will create a new instance of the core app in it's own namespace so that users within that company can use their own subdomain eg. [login to view URL] - Customer Database (MongoDB): Stores all data relating to Customers, and more specifically the namespace that they operate in. Tenant Namespaces: (tenant subdomain eg. [login to view URL]) - Tenant Frontend Angular 8: Core application and specifically login page for users of this tenant. eg. [login to view URL] - Tenant API NodeJS: All endpoints relating to tenant specific queries. - Tenant Database: Stores all data relating to tenants. I am trying to setup this architecture on my local machine with minikube. But I'm having trouble to let the Customer app talk to the core app in custom tenant namespaces and need help with this. I am also new to DevOps so will be open to any suggestions to make changes to the architecture or code.