Deploy Oracle SOA Suite on Oracle Kubernetes Engine (OKE)
Provision a Kubernetes cluster on Oracle Kubernetes Engine with a database for the SOA Suite schemas and a file storage mount path for the domain files, then deploy Oracle SOA Suite in the cluster.
Prerequisites
To deploy Oracle SOA Suite on Container Engine for Kubernetes, ensure that you have sufficient resources and quota for the following:
- One file system.
- One mount target.
- One database: an on-premises database, Oracle Base Database Service, or an Oracle Single Instance Database using Database Operator.
- One Kubernetes cluster and a node pool with enough nodes to meet your requirements.
Note:
- See Domain Resource Sizing and Requirements and Pricing when choosing the node pool shape for Oracle SOA Suite domains. One OCPU is not sufficient.
- The default cluster block volume size may be inadequate. Allocate at least 300 GB for each node. See Resizing a Volume for resizing instructions.
Create a Kubernetes cluster on OKE
Create a Kubernetes cluster using Container Engine for Kubernetes (OKE). See Creating a Cluster for details.
To ensure high availability, Container Engine for Kubernetes:
- Creates the Kubernetes control plane on multiple Oracle-managed nodes, distributing them across availability domains in a region where supported.
- Creates worker nodes in each fault domain within an availability domain, distributing them as evenly as possible across fault domains, subject to other infrastructure restrictions.
Before creating a cluster, review Preparing for Container Engine for Kubernetes and complete the following prerequisites:
- Ensure that you have access to an Oracle Cloud Infrastructure tenancy.
- Check your tenancy's service limits for the components listed in Prerequisites and request a service limit increase if necessary.
- Ensure that you belong to the tenancy's Administrators group and have the appropriate Container Engine for Kubernetes permissions.
- Ensure that you have access to perform Kubernetes operations on a cluster.
Prepare the compartment and policies, then create the cluster and node pool:
-
Create a compartment if one does not already exist for the required network resources, such as a VCN, subnets, an internet gateway, a route table, and security lists.
Network resources can reside in the root compartment. However, if multiple teams will create clusters, use a separate compartment for each team.
See Managing Compartments and Network Resource Configuration for Cluster Creation and Deployment for details.
-
Configure compartment policies. To create or manage clusters, you must belong to one of the following groups:
- The tenancy's Administrators group.
- A group granted the appropriate Container Engine for Kubernetes permissions by a policy.
See Policy Configuration for Cluster Creation and Deployment for details.
-
Create an OKE cluster using the Console, CLI, or API. See Creating a Cluster.
-
Create a managed node pool using the Console, CLI, or API. You can also create managed node pools when creating a cluster in the Console. See Creating a Managed Node Pool.
If the worker nodes are private, set up a bastion host to access them. See Managing Bastions.
Set up access to your cluster
Container Engine for Kubernetes creates a kubeconfig file that you use
to access the cluster with kubectl.
See Setting Up Cluster Access
and configure access using either of the following:
Install tools
After setting up cluster access, verify that the following tools are installed at the required versions, or install them:
kubectl1.24 or later- See Install kubectl for installation instructions.
- Helm 3.10.2 or later
- Helm is a Kubernetes deployment package manager. See Installing Helm to install it locally.
Create storage for the domain home
Use the File Storage service to provision persistent volume claims (PVCs) for the domain home. See Provisioning PVCs on the File Storage Service in the OCI documentation.
The Oracle SOA Suite OKE samples
include files for provisioning a PVC using the CSI volume plugin.
Update fss-dyn-st-class.yaml and
fss-dyn-claim.yaml with the appropriate parameters
to provision the domain PVC.
Set the shared directory's permissions to 1000:0 for the domain home.
See OCI File Storage Persistent Volumes
in the WebLogic Kubernetes Operator documentation.
Create an ingress controller
For clusters created using Container Engine for Kubernetes, configure one of the following ingress controllers:
- The OCI native ingress controller.
- A third-party ingress controller, such as NGINX or Traefik.
See Managing Ingress Controllers. For third-party ingress controller installation instructions, see Setup a Load Balancer.
Set service.type to LoadBalancer
so that OCI provisions the load balancer.
Create an Oracle SOA Suite domain
Prepare the environment as described in Prepare Your Environment, then perform the following steps:
-
Create a Kubernetes secret to pull the Oracle SOA Suite image from the registry:
$ kubectl -n DOMAIN_NAMESPACE create secret docker-registry image-secret \ --docker-server=container-registry.oracle.com \ --docker-username=YOUR_REGISTRY_USERNAME \ --docker-password=YOUR_REGISTRY_PASSWORD \ --docker-email=YOUR_REGISTRY_EMAILReplace
DOMAIN_NAMESPACEwith your namespace. ReplaceYOUR_REGISTRY_USERNAME,YOUR_REGISTRY_PASSWORD, andYOUR_REGISTRY_EMAILwith your registry access details. - When creating persistent storage, set
weblogicDomainStorageTypetoNFSandweblogicDomainStoragePathto the address obtained when creating storage for the domain home. -
Create the domain by following Create Oracle SOA Suite Domains Manually.
The default timeout of 600 seconds may be insufficient for creating a domain on OKE. Use
-tto specify a suitable timeout greater than 600 seconds.
Configure the ingress controller to provide access to the Oracle SOA Suite domain services:
- For the OCI native ingress controller, see Creating Resources for the OCI Native Ingress Controller.
- For third-party ingress controllers, see Setup a Load Balancer for instructions on creating ingress resources.