In this blog post I am going to explain how to create and configure the Kubernetes Cluster in the Oracle Cloud Infrastructure. Oracle offers its own service called Oracle Kubetnetes Engine (OKE).
As a prerequisite, a user must already exist in the cloud who has permission to create and manage the Kubernetes cluster in a compartment. The following policies are necessary to create, update and delete cluster components:
Allow group <group-name> to manage instance-family in <location>
Allow group <group-name> to use subnets in <location>
Allow group <group-name> to read virtual-network-family in <location>
Allow group <group-name> to use vnics in <location>
Allow group <group-name> to inspect compartments in <location>
In the previous blog post I explained the creation and configuration of the instance pool and autoscaling configuration.
If you run farm from the web server and the application server, you should route the client accesses to these servers via a load balancer. The load balancer receives the client requests and distributes them within the server pool.
In this blog post I am going to explain the provisioning of the compute pool node with autoscaling configuration. I have already created the VM instance-bne and installed the Nginx web server in the VM.
During the provisioning of the Linux VM I added the Cloud-Init script as the advanced option that executes the installation and configuration of the Nginx webserver in my vm:
Every cloud administrator wants to administer and monitor their cloud resources from a central location. The Cloud (OCI) Command-Line interface OCI CLI enables this. In this blog post I will describe the installation and configuration of the Cloud CLI on an Linux Server with OS Oracle Enterprise Linux.
To install and use the Cloud CLI you must have the following data:
OCI User: Users for connecting to cloud services
A SSH Keypair used for signing API requests, with the public key uploaded to Oracle OCI
In this post, I will explain the configuration of Middleware components needed to present apex content in web. We will build the separate VM (EC2 Container) in AWS and configure following components: ORDS, Apache Tomcat und Nginx Server.
Installing and Configuring the VM for the APEX Listener