Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Before installing Usage Engine Private Edition, you need to set up a Kubernetes cluster on OCI OKE (Oracle’s managed Kubernetes service).

First, you need to create a basic Kubernetes cluster needs to be created. This You can be done do this in two different ways:

  • Using the terraform tool.

  • Using the OCI management console.

In this guide, terraform will be used. Mainly , mainly because it will enable you to create the basic Kubernetes cluster in minutes with just a single command.

Once the basic Kubernetes cluster has been created, you need to add additional infrastructure needs to be added. For this terraform is also used. You can use terraform for this as well.

Before proceeding, go to Release Information, and download the oci.tar.gz file for the Usage Engine Private Edition version that is being installedyou want to install. Once downloaded, extract its content to a suitable location.

Assumptions

There are a few assumptions been made when using terraform to create cluster resources:

  1. We assume that you have an existing parent domain i.e. , in the example below example.com, hosted on the same account as the cluster that we are going to create in the coming following section and that you wish want to access the cluster environment through via the hostname. Terraform will create a subdomain in the following format: <cluster_name>.<domain>.

    1. cluster name: uepe-oke

    2. domain: example.com

    3. final domain: uepe-oke.example.com

  2. In addition, we We also assume that terraform is allowed to add a NS (NameServer) record to the parent domain . This which is needed to allow DNS delegation from the parent domain to subdomain.

  3. Terraform needs to persist the state of your provisioned infrastructure. By default, by default the state file is stored locally on the computer that terraform is executed from. However, if you have multiple person persons are working on the infrastructure, then it is recommended to store the state file on using a remote persistent persistence such as Object Storage, see https://docs.oracle.com/en-us/iaas/Content/API/SDKDocs/terraformUsingObjectStore.htm for more information.

  4. We use the The OCI File System service (NFS) is used as the default persistent storage for data that needs to be persisted.

  5. We use the The OCI Managed PostgreSQL service for is used as the Usage Engine Private Edition database.

  6. User The user Principle is used through out throughout the entire installation. User must get ready with The user must prepare the private key file locally. User may The user can create and download the private key via the OCI console , through by selecting Profile | My Profile | API keys | Add API key.

Create Basic Cluster and additional infrastructure

The following steps explains how to To create a basic Kubernetes cluster with public and private VPC:

  1. Go to <the location <folder where you extracted the oci.tar.gz file>/oci/terraform and copy theterraform.tfvars.example to terraform.tfvars.

  2. Edit the terraform.tfvars file.

  3. Specify the desired cluster name, OCI region and kubernetes_version (please refer to the see Compatibility Matrix (4.12) to find out which Kubernetes versions that are compatible with this release of Usage Engine Private Edition). Also specify Specify your OCI tenancy_ocid, user_ocid, fingerprint, compartment_ocid and private_key_path (which can be found on the OCI dashboard’s Profile page), as well as the desired number of nodes per cluster (oke_num_nodes).

  4. If you will be running with a database other are going to use another database than Derby also , specify db_password, db_version and db_username.

terraform.tfvars

Where to get the value from?

tenancy_ocid

In the OCI management console, this the tenancy_ocid is listed on Profile | Tenancy: <tenant-name> | Tenancy Details.

fingerprint

Fingerprint is only available after when the user has created the API keys. Refer to , see private_key_path row in the same table below.

In the OCI management console, this the fingerprint is listed on Profile | My Profile | Resources | API keys after when the API keys being have been created.

user_ocid

In the OCI management console, this user_ocid is listed on Profile | My Profile

private_key_path

The full path to your private key file’s filename.

To create and download your private key, go to Profile | My Profile | Resources | API keys, create your API key and click downloadDownload.

region

The region in which you will install your cluster. (, for example "eu-frankfurt-1").

cluster_name

A name for your cluster. Cluster names must start with a lowercase letter followed by up to 39 lowercase letters, numbers or hyphens. They can't cannot end with a hyphen. The cluster name must be unique in the project.

domain

Your existing domain name. In the OCI management console, this is the DNS name that is listed on page Networking |DNS management | Zones.

The service hostname that created by Usage Engine Private Edition will be accessible in the following format: <service_name>.<cluster_name>.<domain> i.e. desktop-online.uepe-oke.example.com.

kubernetes_version

The kubernetes version for kubernetes in alpha numeric string (, for example “v1.29.1").

oke_num_nodes

Number The number of cluster nodes in numeric (format, for example “3).

oke_availability_domain

Availability The availability domain name for the cluster. (, for example "Vafx:EU-FRANKFURT-1-AD-1").

db_password

Choose a secure password for the system database administrator.Minimum , minimum 10 characters.

db_version

Database The database version in numeric string (format, for example “14).

oke_image_id

The OCID of the image to be used for worker node instance creation.

To find out see the available image under your compartment, use the command:

Code Block
oci ce node-pool-options get --node-pool-option-id all --compartment-id <your compartment ocid>.

db_enabled

Boolean flag to enable db_enables is a boolean flag for enabling cloud SQL database resource creation.

fss_enabled

Boolean flag to enable fss_enabled is a boolean flag for enabling file storage resource creation. It is set to false by default. Set it to true if you need persistent file storage is needed.

auto_create_ns_record

Boolean flag to enable auto_create_ns_record is a boolean flag for enabling subdomain NS record auto creation in to be automatically created in the parent domain. In case If your parent domain is not under the same compartment, or if your parent domain is hosted in another cloud provider, then you must set it to false.

Info

Example

...

Code Block
languagetext
#  ____  _____ _____   _____ _   _ _____ ____  _____
# / ___|| ____|_   _| |_   _| | | | ____/ ___|| ____|_
# \___ \|  _|   | |     | | | |_| |  _| \___ \|  _| (_)
#  ___) | |___  | |     | | |  _  | |___ ___) | |___ _
# |____/|_____| |_|     |_| |_| |_|_____|____/|_____(_)

# The below values must be set explicitly in order for the setup to work correctly.

tenancy_ocid     = "ocid1.tenancy.oc1..aaaaaaaamnl7f7t2yrlas2si7b5hpo6t23dqi6mjo3eot6ijl2nqcog5h6ha"
fingerprint      = "7d:67:b3:9d:a3:8f:6d:37:f3:e9:7d:e5:45:ec:df:56"
user_ocid        = "ocid1.user.oc1..aaaaaaaauhk3uhiryg7sw2xjmvf45zasduqwr2cium53gmdxwipe4iqdrfuq"
private_key_path = "/Users/kamheng.choy/Downloads/kamheng.choy@digitalroute.com_2024-04-07T10_07_56.490Z.pem"

# Deployment compartment
compartment_ocid = "ocid1.compartment.oc1..aaaaaaaa56wmblidgvvicamsqkf7sqcqu5yxdhvu3wlvomzgonhflcrv6kcq"

# region
region = "eu-frankfurt-1"

# Name of the cluster, it must be unique in the project.
cluster_name = "test-uepe-cluster-1"

# Domain DNS name
# We'll create a subdomain zone from parent domain, the final domain will be in format "<cluster_name>.<domain>".
# Please note that if this domain is hosted on another OCI project or other cloud provider, then you must
# set auto_create_ns_record = false and manually add the subdomain NS record to the parent domain.
# auto_create_ns_record = false
domain = "stratus.oci.digitalroute.net"

# Admin user password to the database
db_password = "
Password123$
super_SeCrEt_db_pAsSwOrD_457!"

#  _______        _______    _    _  __    _    ____  _     _____
# |_   _\ \      / / ____|  / \  | |/ /   / \  | __ )| |   | ____|_
#   | |  \ \ /\ / /|  _|   / _ \ | ' /   / _ \ |  _ \| |   |  _| (_)
#   | |   \ V  V / | |___ / ___ \| . \  / ___ \| |_) | |___| |___ _
#   |_|    \_/\_/  |_____/_/   \_\_|\_\/_/   \_\____/|_____|_____(_)

# The below sections are the default values, tweak them to your needs.

# Kubernetes version
kubernetes_version = "v1.29.1"

# Number of nodes per cluster
oke_num_nodes = 3
# Worker node machine type
node_pool_shape = "VM.Standard.E4.Flex"
oke_availability_domain = "Vafx:EU-FRANKFURT-1-AD-1"

oke_image_id = "ocid1.image.oc1.eu-frankfurt-1.aaaaaaaapwbqurbd2hpmj2at354r3dkok4o4644am4hwgdagoekpcaon7shq"

# IP CIDR range allocate to the control plane
vcn_cidr_blocks = "10.0.0.0/16"

# Network file system (NFS) persistent storage
fss_enabled = true
filestore
fss_availability_domain = "Vafx:EU-FRANKFURT-1-AD-1"

# Cloud SQL database
db_enabled = true
# DB instance type
db_instance_shape = "PostgreSQL.VM.Standard.E4.Flex.4.64GB"
# DB version
db_version = "14"

...

Note

...

Note!

If your parent domain zone is not under the same project:

...

  • Set auto_create_ns_record = false to disable subdomain NS record auto creation in the parent domain.

  • Perform terraform apply.

...

  • When terraform has been applied, copy the name

...

  • server's value from the terraform output and manually add them to parent domain as a NS record. If you are not using OCI DNS as the parent domain,

...

  • see your Domain Registrar documentation for information on how to add NS record.

  1. Run the following commands:

Code Block
terraform init
terraform plan
terraform apply
  1. Wait for until the terraform commands to finish.have completed and you see the following kind of information:

Code Block
languagetext
Apply complete! Resources: 35 added, 0 changed, 0 destroyed.

Outputs:

backend_nsg = "ocid1.networksecuritygroup.oc1.eu-frankfurt-1.aaaaaaaacreo4kf5kd2n7nk4fn2kcsuv6kye2noowhpjypcmrqmms32gpg3a"
cluster_dns_zone_name = "
cluster_dns_zone_name = "test-uepe-cluster-1.stratus.oci.digitalroute.net"test-uepe-cluster-1.stratus.oci.digitalroute.net"
cluster_dns_zone_name_servers = [
  "ns1.p201.dns.oraclecloud.net.",
  "ns2.p201.dns.oraclecloud.net.",
  "ns3.p201.dns.oraclecloud.net.",
  "ns4.p201.dns.oraclecloud.net.",
]
cluster_dns_zone_ocid = "ocid1.dns-zone.oc1..aaaaaaaacd5nsfzmir3efo5e2pcuga4t622vcxcqkc3ezizl64e5gofo7dza"
cluster_name = "test-uepe-cluster-1"
cluster_ocid = "ocid1.cluster.oc1.eu-frankfurt-1.aaaaaaaaerg6ctgepnuaipifispmuweqi5nvfhswxpu3luuctcvitslu3fea"
compartment_ocid = "ocid1.compartment.oc1..aaaaaaaa56wmblidgvvicamsqkf7sqcqu5yxdhvu3wlvomzgonhflcrv6kcq"
db_admin_user = "postgres"
db_endpoint = "db5j5pt3qwjqmmjgfremgugr7cxtsq-dbinstance-70c946d1330e.postgresql.eu-frankfurt-1.oc1.oraclecloud.com"
db_port = 5432
filesystem_mount_path = "/uepe"
filesystem_ocid = "ocid1.filesystem.oc1.eu_frankfurt_1.aaaaaaaaaais2zcnmzzgcllqojxwiotfouwwm4tbnzvwm5lsoqwtcllbmqwtgaaa"
kms_key_ocid = ""
loadbalancer_ocid = "ocid1.loadbalancer.oc1.eu-frankfurt-1.aaaaaaaanmx4u2yllufrjetacqt5bsgiyznkg7fif3bjfl36xoduyngesvra"
loadbalancer_subnet_ocid = "ocid1.subnet.oc1.eu-frankfurt-1.aaaaaaaapyqsowgik7gak3wkihsm3jtronnc5klbf46jerjnudrqsnlbco5q"
mount_target_IP_address = "10.0.4.212"
mount_target_subnet_ocid = "ocid1.subnet.oc1.eu-frankfurt-1.aaaaaaaaoh36ywx4rki7qtre33f53amjy2zylm6mnqeix6cydn5ul4shfqja"
region = "eu-frankfurt-1"
tenancy_ocid = "ocid1.tenancy.oc1..aaaaaaaamnl7f7t2yrlas2si7b5hpo6t23dqi6mjo3eot6ijl2nqcog5h6ha"
Info

Make sure Ensure to save the output from terraform above . Reason being that it is since it will be used as input throughout the remainder of this installation guide.

A basic Kubernetes cluster has now been set up successfully.A .

Insert excerpt
General Kubernetes Preparations
General Kubernetes Preparations
nameterraform state message
nopaneltrue

An RDS PostgreSQL database instance is up and running on a private subnet VPC with default listening port 5432. The default database postgres is accessible within the cluster at end point db5j5pt3qwjqmmjgfremgugr7cxtsq-dbinstance-70c946d1330e.postgresql.eu-frankfurt-1.oc1.oraclecloud.com with admin username postgres.

You can check see the status of the cluster, db and the other resources in the OCI dashboard.

Configure Cluster Access

To configure cluster access, run the following command:

Code Block
languagebash
oci ce cluster create-kubeconfig --cluster-id <cluster ocid> --file ./kubeconfig.yaml --region eu-frankfurt-1 --token-version 2.0.0  --kube-endpoint PUBLIC_ENDPOINT

The above oci command will generate a A ./kubeconfig.yaml file containing information on how to connect to your newly created cluster . Make sure to set will be generated. Set the KUBECONFIG environment variable to point to that file by running the following command:

Code Block
export KUBECONFIG=<full path to ./kubeconfig.yaml>

...

You can check the status of the cluster nodes like thisby running the following command:

Code Block
kubectl get nodes

For In this example cluster, the output will looks look something like this:

Code Block
NAME         STATUS   ROLES   AGE   VERSION
10.0.2.111   Ready    node    27h   v1.29.1
10.0.2.158   Ready    node    27h   v1.29.1
10.0.2.230   Ready    node    27h   v1.29.1

...

Insert excerpt
General Kubernetes Preparations
General Kubernetes Preparations
namecommon-namespace
nopaneltrue

Now This section is now complete and you can proceed to the Kubernetes Cluster Add-ons - OCI (4.2) section.