Ingress Naming (Compulsory)

An important section which enable users to communicate to Utopia application.

Essentially the app has multiple features exposed to users and Utopia management team which require access via a browser. Between the ingress controller Loadbalancer and the ingress itself, these will help direct traffic from these end points to the applicable application service.

Whether on an internal or External DNS server, you will need to create 'A' records to resolve these endpoints to the Loadbalancer IP address. The IP address will be assigned by the Loadbalancer, so depending on your setup this may be difficult to get before the installation process.

If you are going to expose these servers externally, then make sure you choose ingress names that include a subdomain that you own, so that you can create these records correctly. The ingress will be generated with these names.

Naming these is up to you, but here are some definitions to help you understand what they do:

Utopia UI - The User Interface, users will navigate here in their browser to access Utopia application Identity Server - The UI will redirect users here to login and for Registrations SMTP Server - This will manage email serves for the application Microservices - Apart from managing the workloads of the application, Utopia app managers can access two Dashboards from here eg: microservices.yourdomain.com/hangfire - Utopia job que and job processing and /elmah for detailed system error logs. you can read more about this in the Product Guide section. Third Party API - Utopia allows users to easily create flexible REST API endpoints and webhooks. This application manages this and this url will form part of the generated REST API Listener urls. Utopia UI API - This is the backend to the UI