Proactive insights, news and tips from Oracle WebLogic Server Support. Learn Oracle from Oracle.

Updated WebLogic Kubernetes Support with Operator 2.0

Monica Riccelli
Product Manager

We are excited to announce the release of version 2.0 of the WebLogic Server Kubernetes Operator. The operator uses a common set of Kubernetes APIs to provide an improved user experience when automating operations such as: provisioning, lifecycle management, application versioning, product patching, scaling, and security.  This version of the operator evolves WebLogic to run more natively in cloud neutral infrastructures.  It adds support for WebLogic domain configurations that are included in the Docker images, making these images portable across environments and improving support for CI/CD deployments.  The operator is developed as an open source project fully supported by Oracle. The project can be found in our GitHub repository, and the images are available to be pulled from Docker Hub.

In this version of the WebLogic Server Kubernetes Operator, we have added the following functionality and support for:

  • Kubernetes versions 1.10.11+, 1.111.5+, and 1.12.3+.
  • A Helm chart to install the operator.
  • Creating a WebLogic domain in a Docker image.  We have developed samples in our Docker GitHub project for creating these images with the WebLogic Deployment Tooling (WDT) or with WebLogic Scripting Tool (WLST).  Samples for deploying these images with the operator can be found in the GitHub project.
  • Creating WebLogic domains in a Kubernetes persistent volume or persistent volume claims (PV/PVC). This persistent volume can reside in an NFS file system or other Kubernetes volume types. See our samples to create PV or PCV and to deploy the WebLogic domain in the persistent volume.
  • When the WebLogic domain, application binaries, and application configuration are inside of a Docker image, this configuration is immutable.  We offer configuration overrides for certain aspects of the WebLogic domain configuration to maintain the portability of these images between different environments.
  • The Apache HTTP Server, Traefik, and Voyager (HAProxy-backed) Ingress controller running within the Kubernetes cluster for load balancing HTTP requests across WebLogic Server Managed Servers running in clustered configurations.
  • Unlike previous versions of the operator, operator 2.0 no longer deploys load balancers. We provide Helm charts to deploy these load balancers (see the samples listed below):
  • User-initiated lifecycle operations for WebLogic domains, clusters, and servers, including rolling restart.  See the  details in Starting, stopping, and restarting servers.
  • Managing WebLogic configured and dynamic clusters.
  • Scaling WebLogic domains by starting and stopping Managed Servers on demand, or by integrating with a REST API to initiate scaling based on the WebLogic Diagnostic Framework (WLDF), Prometheus, Grafana, or other rules.  If you want to learn more about scaling with Prometheus, read the blog  Using Prometheus to Automatically Scale WebLogic Clusters on Kubernetes.  Also, see this blog which walks you through a sample of scaling with WLDF, WebLogic Dynamic Clusters on Kubernetes.
  • Exposing T3 channels outside the Kubernetes domain, if desired.
  • Exposing HTTP paths on a WebLogic domain outside the Kubernetes domain with load balancing.  Updating the load balancer when a Managed Server is added or removed from a cluster during scaling up or shrinking actions.
  • Publishing operator and WebLogic Server logs into Elasticsearch and interacting with them in Kibana.  See our documentation, Configuring Kibana and Elasticsearch.

Our future plans include formal certification of WebLogic Server on Open Shift.  If you are interested in deploying a WebLogic domain and operator 2.0 in Open Shift, read the blog, Running WebLogic on Open Shift.  We are building and open-sourcing a new tool, the WebLogic Logging Exporter, to export WebLogic Server logs directly to the Elastic Stack.  Also, we are publishing blogs that describe how to take advantage of the new functionality in operator 2.0. Please stay tuned for more information. The fastest way to experience the operator is to follow the Quick Start guide.  We hope this announcement is helpful to those of you seeking to deploy WebLogic Server on Kubernetes, and look forward to your feedback.


Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.