This installation guide will tell describes how you how to perform a reference installation of Usage Engine Private Edition. It is aimed at providing aims to provide you with a good starting point. It is not aimed at providing , ot to provide you with a fully-fledged production-grade Kubernetes cluster.
You will end up with 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.
...
| Info |
|---|
The diagram only shows the main components that this installation guide covers. For a full description of the Usage Engine Private Edition architecture, please refer to: |
...
Here follows information about the purpose of the main components in the diagram:
Component | Purpose |
|---|---|
external-dns | Makes Kubernetes resources (services, ingresses) discoverable via public DNS servers by automatically configuring the DNS management service. |
platform desktop-online uepe-operator | These components are all pat of the Usage Engine Private Edtion Edition helm chart. For detailed information about these components, please refer to: |
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, please refer to: see |
cert-manager | To automate Automates management of TLS certificates. Although optional, it is the recommended solution to provide apply TLS to Usage Engine Private Edition. For additional information, please refer to: |
...