System Requirements for OIG on Kubernetes

5 System Requirements for OIG on Kubernetes

This section provides information about the system requirements and limitations for deploying and running Oracle Identity Management (OIG) on Kubernetes with the WebLogic Kubernetes Operator 4.2.10.

Kubernetes Requirements

You must have a running Kubernetes cluster that meets the following requirements:

The Kubernetes cluster and container engine must meet the minimum version requirements outlined in document ID 2723908.1 on My Oracle Support.
An administrative host from which to deploy the products: This host could be a Kubernetes Control host, a Kubernetes Worker host, or an independent host. This host must have kubectl deployed using the same version as your cluster.
The Kubernetes cluster must have sufficient nodes and resources.
You must have the cluster-admin role to install the WebLogic Kubernetes Operator.
An installation of Helm is required on the Kubernetes cluster. Helm is used to create and deploy the necessary resources on the Kubernetes cluster.
A supported container engine such as CRI-O or Docker must be installed and running on the Kubernetes cluster.
The nodes in the Kubernetes cluster must have access to a persistent volume such as a Network File System (NFS) mount, or a shared file system.
The system clocks on node of the Kubernetes cluster must be synchronized. Run the date command simultaneously on all the nodes in each cluster and then synchronize accordingly.

Note:

This documentation does not tell you how to install a Kubernetes cluster, Helm, or the container engine. Please refer to your vendor specific documentation for this information. Also see System Requirements for OIG on Kubernetes.

Database Requirements

You must have a running Oracle Database that meets the following requirements:

Oracle Database 19.23 or later. The database must be a supported version for OIG as outlined in Oracle Fusion Middleware 14c Certifications.
The database must meet the requirements as outlined in About Database Requirements for an Oracle Fusion Middleware Installation and in RCU Requirements for Oracle Databases.
It is recommended that the database initialization parameters are set as per Minimum Initialization Parameters.

Container Registry Requirements

You must have your own container registry to store container and domain images in the following circumstances:

If your Kubernetes cluster does not have network access to Oracle Container Registry, then you must have your own container registry to store the OIG container images.
If you intend to deploy OIG with WDT models, you must have a container registry to store the domain image.

Your container registry must be accessible from all nodes in the Kubernetes cluster.

Alternatively if you don’t have your own container registry, you can load the images on each worker node in the cluster. Loading the images on each worker node is not recommended as it incurs a large administrative overhead.

Note:

This documentation does not tell you how to install a container registry. Please refer to your vendor specific documentation for this information.