...
You will end up with 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.
...
Component | Purpose |
|---|---|
external-dns | Makes Kubernetes resources (services, ingresses) discoverable via public DNS servers by automatically configuring the Route 53 DNS management service. |
platform desktop-online uepe-operator | These components are all pat of the Usage Engine Private Edtion 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: |
cert-manager | To automate management of TLS certificates. Although optional, it is the recommended solution to provide TLS to Usage Engine Private Edition. For additional information, please refer to: |
...