Get started

An operator is an application-specific controller that extends Kubernetes to create, configure, and manage instances of complex applications. The Oracle WebLogic Server Kubernetes Operator follows the standard Kubernetes operator pattern, and simplifies the management and operation of WebLogic domains and deployments.

You can have one or more operators in your Kubernetes cluster that manage one or more WebLogic domains each. We provide a Helm chart to manage the installation and configuration of the operator. Detailed instructions are available here.

Operator prerequisites

  • Kubernetes 1.11.5+, 1.12.3+, 1.13.0+, and 1.14.0+ (check with kubectl version).
  • Flannel networking v0.9.1-amd64 (check with docker images | grep flannel).
  • Docker 18.9.1 (check with docker version) or CRI-O 1.14.7 (check with crictl version | grep RuntimeVersion).
  • Helm 2.14.3+ (check with helm version).
  • Oracle WebLogic Server 12.2.1.3.0 with patch 29135930.
    • The existing WebLogic Docker image, container-registry.oracle.com/middleware/weblogic:12.2.1.3, has all the necessary patches applied.
    • Check the WLS version with docker run container-registry.oracle.com/middleware/weblogic:12.2.1.3 sh -c 'source $ORACLE_HOME/wlserver/server/bin/setWLSEnv.sh > /dev/null 2>&1 && java weblogic.version'.
    • Check the WLS patches with docker run container-registry.oracle.com/middleware/weblogic:12.2.1.3 sh -c '$ORACLE_HOME/OPatch/opatch lspatches'.
  • You must have the cluster-admin role to install the operator.
  • We do not currently support running WebLogic in non-Linux containers.

Cloud providers

The Oracle Global Pricing and Licensing site provides details about licensing practices and policies. WebLogic Server and the operator are supported on “Authorized Cloud Environments” as defined in this Oracle licensing policy and this list of eligible products.

The official document that defines the supported configurations is here.

In accordance with these policies, the operator and WebLogic Server are supported on Oracle Cloud Infrastructure using Oracle Container Engine for Kubernetes, or in a cluster running Oracle Linux Container Servies for use with Kubernetes on OCI Compute; and on “authorized cloud environments”.

OpenShift

Operator 2.0.1+ is certified for use on OpenShift Container Platform 3.11.43+, with Kubernetes 1.11.5+. OpenShift 4 certification is currently in progress.

When using the operator in OpenShift, the anyuid security context constraint is required to ensure that WebLogic containers run with a UNIX UID that has the correct permissions on the domain filesystem. For more information, see OpenShift in the Security section.

Important note about development-focused Kubernetes distributions

There are a number of development-focused distributions of Kubernetes, like kind, Minikube, Minishift and so on. Often these run Kubernetes in a virtual machine on your development machine. We have found that these distributions present some extra challenges in areas like:

  • Separate Docker image stores, making it necessary to save/load images to move them between Docker file systems,
  • Default virtual machine file sizes and resource limits that are too small to run WebLogic or hold the necessary images,
  • Storage providers that do not always support the features that the operator and/or WebLogic rely on,
  • Load balancing implementations that do not always support the features that the operator and/or WebLogic rely on.

As such, we do not recommend using these distributions to run the operator and/or WebLogic, and we do not provide support for WebLogic or the operator running in these distributions.

We have found that Docker for Desktop does not seem to suffer the same limitations, and we do support that as a dev/test option.

Operator Docker image

You can find the operator image in Docker Hub.