navigation

Oracle WebLogic Server Kubernetes Operator

The WebLogic Server Kubernetes Operator (the “operator”) supports running your WebLogic Server and Fusion Middleware Infrastructure domains on Kubernetes, an industry standard, cloud neutral deployment platform. It lets you encapsulate your entire WebLogic Server installation and layered applications into a portable set of cloud neutral images and simple resource description files. You can run them on any on-premises or public cloud that supports Kubernetes where you’ve deployed the operator.

Furthermore, the operator is well suited to CI/CD processes. You can easily inject changes when moving between environments, such as from test to production. For example, you can externally inject database URLs and credentials during deployment or you can inject arbitrary changes to most WebLogic configurations.

The operator takes advantage of the Kubernetes operator pattern, which means that it uses Kubernetes APIs to provide support for operations, such as: provisioning, lifecycle management, application versioning, product patching, scaling, and security. The operator also enables the use of tooling that is native to this infrastructure for monitoring, logging, tracing, and security.

You can:

  • Deploy an operator that manages all WebLogic domains in all namespaces in a Kubernetes cluster, or that only manages domains in a specific subset of the namespaces, or that manages only domains that are located in the same namespace as the operator. At most, a namespace can be managed by one operator.
  • Supply WebLogic domain configuration using:
    • Domain in PV: Locates WebLogic domain homes in a Kubernetes PersistentVolume (PV). This PV can reside in an NFS file system or other Kubernetes volume types.
    • Domain in Image: Includes a WebLogic domain home in a container image.
    • Model in Image: Includes WebLogic Server Deploy Tooling models and archives in a container image.
  • Configure deployment of WebLogic domains as a Kubernetes resource (using a Kubernetes custom resource definition).
  • Override certain aspects of the WebLogic domain configuration; for example, use a different database password for different deployments.
  • Start and stop servers and clusters in the domain based on declarative startup parameters and desired states.
  • Scale WebLogic domains by starting and stopping Managed Servers on demand, or by integrating with a REST API to initiate scaling based on the WebLogic Diagnostics Framework (WLDF), Prometheus, Grafana, or other rules.
  • Expose the WebLogic Server Administration Console outside the Kubernetes cluster, if desired.
  • Expose T3 channels outside the Kubernetes domain, if desired.
  • Expose HTTP paths on a WebLogic domain outside the Kubernetes domain with load balancing, and automatically update the load balancer when Managed Servers in the WebLogic domain are started or stopped.
  • Publish operator and WebLogic Server logs into Elasticsearch and interact with them in Kibana.

The fastest way to experience the operator is to follow the Quick Start guide, or you can peruse our documentation, read our blogs, or try out the samples. Also, you can step through the Tutorial using the operator to deploy and run a WebLogic domain container-packaged web application on an Oracle Cloud Infrastructure Container Engine for Kubernetes (OKE) cluster.


Current production release

The current release of the operator is 3.2.2. This release was published on April 27, 2021. See the operator prerequisites and supported environments here.


Recent changes and known issues

See the Release Notes for recent changes to the operator and known issues.

Operator earlier versions

Documentation for prior releases of the operator: 2.5.0, 2.6.0, 3.0.x, and 3.1.x.

Backward compatibility guidelines

Starting from the 2.0.1 release, operator releases are backward compatible with respect to the domain resource schema, operator Helm chart input values, configuration overrides template, Kubernetes resources created by the operator Helm chart, Kubernetes resources created by the operator, and the operator REST interface. We intend to maintain compatibility for three releases, except in the case of a clearly communicated deprecated feature, which will be maintained for one release after a replacement is available.

About this documentation

This documentation includes sections targeted to different audiences. To help you find what you are looking for more easily, please consult this table of contents:

  • The Quick Start guide explains how to quickly get the operator running, using the defaults, nothing special.
  • The User guide contains detailed usage information, including how to install and configure the operator, and how to use it to create and manage WebLogic domains.
  • The Samples provide detailed example code and instructions that show you how to perform various tasks related to the operator.
  • The Developer guide provides details for people who want to understand how the operator is built, tested, and so on. Those who wish to contribute to the operator code will find useful information here.
  • Reference describes domain resource attributes and the operator REST API.
  • Security describes Kubernetes, WebLogic, and OpenShift security requirements.
  • Frequently asked questions provides answers to common questions.

Oracle support

To access Oracle support for running WebLogic Server domains on Kubernetes platforms, see WebLogic Server Certifications on Kubernetes in My Oracle Support Doc ID 2349228.1.

Need more help? Have a suggestion? Come and say, “Hello!”

We have a public Slack channel where you can get in touch with us to ask questions about using the operator or give us feedback or suggestions about what features and improvements you would like to see. We would love to hear from you. To join our channel, please visit this site to get an invitation. The invitation email will include details of how to access our Slack workspace. After you are logged in, please come to #operator and say, “hello!”