...
Here follows information about the purpose of the main resources components in the diagram:
ResourceComponent | Purpose |
|---|---|
external-dns | Makes Kubernetes resources (services, ingresses) discoverable via public DNS servers by automatically configuring the Route 53 DNS service. |
aws-load-balancer-controller | Provisions application load balancer to satisfy ingress resources. Provisions network load balancer to satisfy service resources. For additional information, please refer to: |
ingress-alb | An ingress that gets created as part of installing Usage Engine Private Edition. |
efs-csi-controller | This is optional and only required if your business logic implementation (workflow configuration) requires persistent file storage. Its purpose is to dynamically provision a persistent volume (pv) whenever a persistent volume claim (pvc) is created. The pv is provisioned based on the storage class (sc) that the pvc references. For additional information, please refer to: |
mz-bundled-pvc | A pvc that gets created when installing Usage Engine Private Edition. It only gets created under the condition that persistence is enabled in the Usage Engine Private Edition helm chart. This is optional and only required if your business logic implementation (workflow configuration) requires persistent file storage. |
platform desktop-online uepe-operator | These resources components are all pat of the Usage Engine Private Edtion helm chart. For detailed information about these resourcescomponents, 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: |
...