Prerequisites

To deploy Oracle SOA Suite on Container Engine for Kubernetes, ensure you have available resources and quota for:

• One file storage systems.
• One mount target.
• One Database, either an on-premise Database or Oracle Base Database Service or Oracle Single Instance Database using Database Operator.
• One Kubernetes cluster and a node pool with the required number of nodes as per your requirement.

Create a Kubernetes cluster on OKE

You can create a Kubernetes cluster using Container Engine for Kubernetes (OKE). See here for details.

To ensure high availability, Container Engine for Kubernetes:

• Creates the Kubernetes Control Plane on multiple Oracle-managed control plane nodes (distributing the control plane nodes across different availability domains in a region, where supported).
• Creates worker nodes in each of the fault domains in an availability domain (distributing the worker nodes as evenly as possible across the fault domains, subject to any other infrastructure restrictions).

Preparing for OKE

Before you start creating the Container Engine for Kubernetes, refer the Preparing for Container Engine for Kubernetes and find out if you have met some of the below requirements:

• Access to an Oracle Cloud Infrastructure tenancy.
• Check the service limits for the components listed in Prerequisites in your Oracle Cloud Infrastructure tenancy and, if necessary, request a service limit increase.
• Belong to tenancy's Administrators group and also have appropriate Container Engine for Kubernetes permissions
• Access to perform Kubernetes operations on a cluster.

Create a compartment

Within your tenancy, there must already be a compartment to contain the necessary network resources (such as a VCN, subnets, internet gateway, route table, security lists). If such a compartment does not exist already, you will have to create it. Note that the network resources can reside in the root compartment. However, if you expect multiple teams to create clusters, best practice is to create a separate compartment for each team.

Refer Managing Compartments and Network Resource Configuration for Cluster Creation and Deployment for more details.

Create compartment policies

To create and/or manage clusters, you must belong to one of the following:

• The tenancy's Administrators group
• A group to which a policy grants the appropriate Container Engine for Kubernetes permissions.

See Policy Configuration for Cluster Creation and Deployment for details.

Create an OKE Cluster

Create a new Kubernetes clusters using Container Engine for Kubernetes to create new Kubernetes clusters. You can create clusters using the Console, the CLI, and the API. See Creating a Cluster for details.

Create node pool

When you create a new cluster using the Console, can create managed node pools using the Console. See here to create new managed node pools using the Console, the CLI, or the API. If your worker nodes are configured as private, you will need to establish a bastion host to access them. Refer Managing Bastions.

Set up access to your Cluster

Container Engine for Kubernetes creates a Kubernetes kubeconfig configuration file that you use to access the cluster using kubectl. Refer Setting Up Cluster Access and create access via Cloud Shell or Local access.

Install tools

Once you have setup the cluster access, verify or install the below versions of the tools required for deploying Oracle SOA Suite domain: - kubectl (>= 1.24) : See here for the installation instructions. - Helm (>= 3.10.2): Helm is a Kubernetes deployment package manager. See here to install helm locally.

Create storage for domain home

You can use the File Storage service to provision persistent volume claims which will be used for domain home. Refer Provisioning PVCs on the File Storage Service for details in the OCI documentation. Sample files are available for provisioning a PVC using the CSI Volume Plug in. You can update the fss-dyn-st-class.yaml and fss-dyn-claim.yaml files with the relevant parameters to provision the PVC for the domain. See WebLogic Kubernetes Operator documentation for updating the permissions of shared directory to 1000:0 for domain home.

Create an ingress controller

See Managing Ingress Controllers.See Setup a Load Balancer for installation details on third-party ingress controller. Note to set the service.type to LoadBalancer, so that OCI provisions the Load Balancer.

Create an Oracle SOA Suite domain

See Prepare Your Environment for preparing the environment for Oracle SOA Suite domains.

Perform the following steps:

1. Create a Kubernetes secret to enable pulling 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_EMAIL
   

   Replace DOMAIN_NAMESPACE, YOUR_REGISTRY_USERNAME, YOUR_REGISTRY_PASSWORD, and YOUR_REGISTRY_EMAIL with the values you use to access the registry.

2. While creating a persistent storage, ensure to set the weblogicDomainStorageType to NFS and weblogicDomainStoragePath to the address obtained in Create Storage for Domain home.

To create the domain, see Create Oracle SOA Suite Domains Manually for details on creation of an Oracle SOA Suite domain. Note that, the default timeout value of 600s may not be sufficient for creating the domain on OKE, hence pass a sufficient timeout value greater than 600 with -t.

Configure ingress controller to access Oracle SOA Suite domain services

Refer OCI documentation, in case you have set up OCI native ingress controller. See Setup a Load Balancer for creating the ingress resources on third-party ingress controllers.