This document provides information about the system requirements and limitations for deploying and running OAM domains with the WebLogic Kubernetes Operator 4.1.2.
A running Kubernetes cluster that meets the following requirements:
cluster-admin role to install the WebLogic Kubernetes Operator.
date command simultaneously on all the nodes in each cluster and then syncrhonize accordingly.
A running Oracle Database 18.104.22.168 or later. The database must be a supported version for OAM as outlined in Oracle Fusion Middleware 12c certifications. It 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.
Note: This documentation does not tell you how to install a Kubernetes cluster, Helm, the container engine, or how to push container images to a container registry. Please refer to your vendor specific documentation for this information. Also see Getting Started.
Compared to running a WebLogic Server domain in Kubernetes using the operator, the following limitations currently exist for OAM domains:
configuredManagedServerCount. For more details on this parameter, see Prepare the create domain script. It is recommended to pre-configure your cluster so it’s sized a little larger than the maximum size you plan to expand it to. You must rigorously test at this maximum size to make sure that your system can scale as expected.