Introduction - OCI (4.2)

This installation guide describes how you perform a reference installation of Usage Engine Private Edition. It aims to provide you with a good starting point, ot to provide you with a fully-fledged production-grade Kubernetes cluster.

When finished you will have a Usage Engine Private Edition installation that is ready for you to start implementing your business logic, in the form of workflow configurations, and eventually creating your first EC Deployment.

The diagram below illustrates what the system will look like after having gone through this installation guide.

The diagram only shows the main components that this installation guide covers. For a full description of the Usage Engine Private Edition architecture, see https://infozone.atlassian.net/wiki/x/IpJkBg.

Here follows information about the purpose of the main components in the diagram:

Component	Purpose

Component	Purpose
external-dns	Makes Kubernetes resources (services, ingresses) discoverable via public DNS servers by automatically configuring the DNS management service. For additional information, please refer to: https://github.com/kubernetes-sigs/external-dns
platform desktop-online uepe-operator	These components are all pat of the Usage Engine Private Edition helm chart. For detailed information about these components, see https://infozone.atlassian.net/wiki/x/IpJkBg.
oci-native-ingress-controller	Provisions application load balancer to satisfy ingress resources. For additional information, please refer to:
ingress-nginx-controller	This is an Ingress controller using NGINX as a reverse proxy and load balancer. This is optional and only required if you plan on creating EC Deployment(s) that use ingress. For addtional information, see
cert-manager	Automates management of TLS certificates. Although optional, it is recommended to apply TLS to Usage Engine Private Edition. For additional information, please refer to: