...
| Code Block | ||
|---|---|---|
| ||
oci:
certificates:
id: ocid1.certificate.oc1.eu-frankfurt-1.amaaaaaaqpnxi2aaftofigjmkytoomv2u2ycjenhvqsbarhfhpycfujihyyq
backendNSG: ocid1.networksecuritygroup.oc1.eu-frankfurt-1.aaaaaaaaephkmmm3hsyqw57wvkfssqlc56ddj7yknhgz7cgajxijvhqkzflq
healthcheck:
desktoponline:
port: 9001
ingressnginx:
port: 443
environment: oci
global:
domain: example-cluster.stratus.oci.digitalroute.net
ingressController:
serviceName: ingress-nginx-controller
imagePullSecrets:
- name: ecr-cred
licenseKey: VGhpcyBpcyBhIGZha2UgVXNhZ2UgRW5naW5lIFByaXZhdGUgRWRpdGlvbiBsaWNlbnNlIGtleSE=
log:
format: json
platform:
db:
type: postgresql
tls:
cert:
public: certManager
certManager:
public:
issuer:
kind: ClusterIssuer
name: example-issuer
enabled: true
postgres:
adminUsername: dbadminpostgres
host: example-cluster-db-primary.postgresql.eu-frankfurt-1.oc1.oraclecloud.com
port: 5432
db: mz
persistence:
enabled: true |
Here follows information on how you can determine the values to set in your particular installation:
Value | Comment | ||
|---|---|---|---|
| This value should be set to match the |
| the ocid of certificate created in previous section. |
| This value should be set to match the ocid of the network security group of backend worker nodes. | ||
| desktop-online backend set health check port, i.e., 9001 | ||
| ingress nginx backend set health check port, i.e., 443 | ||
| This is the name of the Kubernetes | ||
| This value should be set to match the | ||
| This is referencing an image pull secret containing the credentials required in order to pull container images from the Digital Route AWS ECR registry. If you are hosting the container images in your own container registry, depending on how that is configured, another image pull secret is probably needed. See https://infozone.atlassian.net/wiki/spaces/UEPE4D/pages/161481567/Common+Usage+Engine+Private+Edition+Preparations#Container-Images for additional information. | ||
| The license key that can be found in the | ||
| If you need to use dedicated log collection and monitoring tools like Fluent-bit, Elasticsearch, Kibana or AWS CloudWatch for Usage Engine Private Edition, make sure the log format is configured to | ||
| These values are set to use the example issuer created at the beginning of this chapter. This should only be seen as an example and the values should be adjusted according to the real world situation. | ||
| Should be set to match the | ||
| The license key that can be found in the |
| Set to match the RDS PostgreSQL service that was created in the 161481605/General+Pre-requisites#License section). |
| If you need to use dedicated log collection and monitoring tools like Fluent-bit, Elasticsearch, Kibana or AWS CloudWatch for Usage Engine Private Edition, make sure the log format is configured to | ||
| These values are set to use the example issuer created at the beginning of this chapter. This should only be seen as an example and the values should be adjusted according to the real world situation. | ||
| Value is taken from the | ||
| Value is taken from the first part of the | ||
| Value is taken from the second part of the |
| Info |
|---|
General documentation of the values above is provided in the |
...
If you have chosen to prepare for persistent file storage, there are two different ways of configuring your Usage Engine Private Edition installation to use it.
Use Bundled
...
OCI Specific PVC
Specifically for OCI, the Usage Engine Private Edition helm chart contains a bundled persistent volume claim. This persistent volume claim is using the fss-dyn-storage storage class. To enable it, simply set the following helm values:
...