...
In this main installation example, it is assumed that the following optional resources have been added while preparing for the installation (see Kubernetes Cluster Add-ons - OCI (4.23)):
ingress-nginx-controller
cert-manager
...
In this example, we are going to use an ACME issuer type that is configured to match the Kubernetes cluster that was set up previously in the Preparations - OCI (4.23) chapter:
| Code Block | ||
|---|---|---|
| ||
apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
name: example-issuer
spec:
acme:
# The ACME server URL
server: https://acme-v02.api.letsencrypt.org/directory
# Email address used for ACME registration
# You must replace this email address with your own.
# Let's Encrypt will use this to contact you about expiring
# certificates, and issues related to your account.
email: <your valid email address>
# Name of a secret used to store the ACME account private key
privateKeySecretRef:
name: example-issuer-account-key
solvers:
- dns01:
webhook:
groupName: acme.d-n.be
solverName: oci
config:
ociProfileSecretName: oci-profile |
...
| Info |
|---|
In the example below, it is assumed that you have configured the Postgres admin password through a secret. If you have not done so, see https://infozone.atlassian.net/wiki/spaces/UEPE4D/pages/211091666303826032/Usage+Engine+Private+Edition+Preparations+-+OCI+4.2#Bootstrapping3#Bootstrapping-System-Credentials-%5BinlineExtension%5D for guidance. |
...
Value | Comment |
|---|---|
| This value indicates if you to use OCI SSL certificate or Kubernetes secret for Load Balancer SSL termination. The default value is Set it to |
| This value should be set to match the ocid of certificate created in previous section, Import-into-OCI-Certificates-Service. This value is not in used if |
| This value is taken from the |
| This is the desktop-online backend set health check port, 9001. |
| This is the ingress nginx backend set health check port, 443. |
| This is the name of the Kubernetes |
| This value is taken from the |
| This is referencing an image pull secret containing the credentials required in order to pull container images from the DigitalRoute AWS ECR registry. If you are hosting the container images in your own container registry, another image pull secret might be needed, depending on how it is configured. See General Usage Engine Private Edition Preparations (4.23) for additional information. |
| This is 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, ensure that the log format is configured to |
| These values are set to use the example issuer created at the beginning of this page. This should only be seen as an example and the values should be adjusted according to the real world scenario. |
| This value is taken from the |
| This value is taken from the |
| This value is taken from the |
| The persistent volume claim name created in previous section OCI-Add-ons | oci-file-service-storage | Static Provisioning. Ignore if |
...
| Note |
|---|
In the example presented below, the following assumptions have been made:
|
...
You should now be able to access the Desktop Online user interface at:
https://desktop-online.example-cluster.stratus.oci.digitalroute.net/
It may take a little while before the DNS record gets registered.
| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
In this example, my-pvc is an arbitrary persistent volume claim that you have created before hand.
| Insert excerpt | ||||||||
|---|---|---|---|---|---|---|---|---|
|