Supported platforms

Oracle Cloud Infrastructure

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”.

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 Kubernetes Operator are certified and supported on Oracle Linux Cloud Native Environment:

  • Operator v2.6.0 is certified on OLCNE 1.1 and v3.2.5 is certified on OLCNE 1.3.
  • Operator v3.2.5 provides certified support of OLCNE 1.3 with Kubernetes 1.20.6 and CRI-O 1.20.2.

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.

VMware Tanzu Kubernetes Service

Tanzu Kubernetes Grid (TKG) is a managed Kubernetes Service that lets you quickly deploy and manage Kubernetes clusters. The WebLogic Kubernetes Operator and Oracle WebLogic Sever are fully supported and certified on VMware Tanzu Kubernetes Grid Multicloud 1.1.3 (with vSphere 6.7U3).

TKG support and limitations:

  • Both Domain in Image and Model in Image domain home source types are supported. Domain in PV is not supported.
  • VSphere CSI driver supports only volumes with Read-Write-Once policy. This does not allow writing stores on PV.
    • For applications requiring HA, use JMS and JTA stores in the database.
  • The ingress used for certification is NGINX, with MetalLB load balancer.

OpenShift

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+.

To accommodate OpenShift security requirements:

  • For security requirements to run WebLogic in OpenShift, see the OpenShift chapter in the Security section.
  • Beginning with operator version 3.3.2, specify the kubernetesPlatorm Helm chart property with value OpenShift. For more information, see Operator Helm configuration values.

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 container image caches, 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.