WebLogic Kubernetes Operator
The WebLogic 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.
- 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:
- Model in Image: Includes WebLogic Deploy Tooling models and archives in a container image.
- Domain in Image: Includes a WebLogic domain home in a container image.
- 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.
- Configure deployment of WebLogic domains as Kubernetes resources (using Kubernetes custom resource definitions).
- 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, Kubernetes scale commands, setting up a Kubernetes Horizontal Pod Autoscaler, or by integrating with a REST API to initiate scaling based on the WebLogic Diagnostics Framework (WLDF), Prometheus, Grafana, or other rules.
- 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.
- Expose the WebLogic Server Administration Console outside the Kubernetes cluster, if desired.
- Expose T3 channels outside the Kubernetes domain, if desired.
- 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 Container Engine for Kubernetes (OKE) cluster.
Current production release
The current release of the operator is 4.0.1.
This release was published on November 4, 2022. See the operator prerequisites and supported environments.
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, 3.1.x, 3.2.x, 3.3.x, and 3.4.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.
See Get help.