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

For the current production release 3.0.4:

  • Kubernetes 1.14.8+, 1.15.7+, 1.16.0+, 1.17.0+, and 1.18.0+ (check with kubectl version).
  • Flannel networking v0.9.1-amd64 or later (check with docker images | grep flannel), Calico networking (Calico v3.16.1), or OpenShift SDN on OpenShift 4.3 systems.
  • Docker 18.9.1 or 19.03.1 (check with docker version) or CRI-O 1.14.7 (check with crictl version | grep RuntimeVersion).
  • Helm 3.1.3+ (check with helm version --client --short).
  • Either Oracle WebLogic Server with patch 29135930, Oracle WebLogic Server, or Oracle WebLogic Server
    • The existing WebLogic Docker image, , has all the necessary patches applied.
    • Check the WLS version with docker run sh -c 'source $ORACLE_HOME/wlserver/server/bin/ > /dev/null 2>&1 && java weblogic.version'.
    • Check the WLS patches with docker run sh -c '$ORACLE_HOME/OPatch/opatch lspatches'.
  • You must have the cluster-admin role to install the operator. The operator does not need the cluster-admin role at runtime.
  • 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 Services for use with Kubernetes on OCI Compute, and on “Authorized Cloud Environments”.

Microsoft Azure Kubernetes Service

Azure Kubernetes Service (AKS) is a hosted Kubernetes environment. The WebLogic Kubernetes Operator, Oracle WebLogic Sever 12c, and Oracle Fusion Middleware Infrastructure 12c are fully supported and certified on Azure Kubernetes Service (as per the documents referenced above).

AKS support and limitations:

  • Both Domain in Image and Domain in PV domain home source types are supported.
  • For Domain in PV, we support Azure Files volumes accessed through a persistent volume claim; see here.
  • Azure Load Balancers are supported when provisioned using a Kubernetes Service of type=LoadBalancer.
  • Oracle databases running in Oracle Cloud Infrastructure are supported for Fusion Middleware Infrastructure MDS data stores only when accessed through an OCI FastConnect.
  • Windows Server containers are not currently supported, only Linux containers.

Oracle Linux Cloud Native Environment (OLCNE)

Oracle Linux Cloud Native Environment is a fully integrated suite for the development and management of cloud-native applications. Based on Open Container Initiative (OCI) and Cloud Native Computing Foundation (CNCF) standards, Oracle Linux Cloud Native Environment delivers a simplified framework for installations, updates, upgrades, and configuration of key features for orchestrating microservices.

WebLogic Server and the WebLogic Server Kubernetes Operator are certified and supported on Oracle Linux Cloud Native Environment. Operator 2.6.0 provides certified support of OLCNE 1.1 with Kubernetes 1.17.0.


Operator 2.0.1+ is certified for use on OpenShift Container Platform 3.11.43+, with Kubernetes 1.11.5+.

Operator 2.5.0+ is certified for use on OpenShift Container Platform 4.3.0+ with Kubernetes 1.16.2+.

When using the operator in OpenShift, a security context constraint is required to ensure that WebLogic containers run with a UNIX UID that has the correct permissions on the domain file system. This could be either the anyuid SCC or a custom one that you define for user/group 1000. 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 or WebLogic rely on
  • Load balancing implementations that do not always support the features that the operator or WebLogic rely on

As such, we do not recommend using these distributions to run the operator 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 development/test option.

Operator Docker image

You can find the operator image in Docker Hub.