You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+14-4Lines changed: 14 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,14 +8,17 @@ Many organizations are exploring, testing, or actively moving application worklo
8
8
9
9
Oracle has been working with the WebLogic community to find ways to make it as easy as possible for organizations using WebLogic Server to run important workloads, to move those workloads into the cloud. One aspect of that effort is the creation of the Oracle WebLogic Server Kubernetes Operator. This release of the Operator provides a number of features to assist with the management of WebLogic domains in a Kubernetes environment, including:
10
10
11
-
* A mechanism to create a WebLogic domain on a Kubernetes persistent volume.
11
+
* A mechanism to create a WebLogic domain on a Kubernetes persistent volume.This persistent volume can reside in NFS.
12
12
* A mechanism to define a WebLogic domain as a Kubernetes resource (using a Kubernetes custom resource definition).
13
13
* The ability to automatically start servers based on declarative startup parameters and desired states.
14
+
* The ability to manage a WebLogic configured or dynamic cluster.
14
15
* The ability to automatically expose the WebLogic Server Administration Console outside the Kubernetes cluster (if desired).
15
16
* The ability to automatically expose T3 channels outside the Kubernetes domain (if desired).
16
17
* The ability to automatically expose HTTP paths on a WebLogic domain outside the Kubernetes domain with load balancing, and to update the load balancer when Managed Servers in the WebLogic domain are started or stopped.
17
18
* The ability to scale a WebLogic domain by starting and stopping Managed Servers on demand, or by integrating with a REST API to initiate scaling based on WLDF, Prometheus/Grafana, or other rules.
18
-
* The ability to publish Operator and WebLogic Server logs into ElasticSearch and interact with them in Kibana.
19
+
* The ability to publish Operator and WebLogic Server logs into Elasticsearch and interact with them in Kibana.
20
+
21
+
19
22
20
23
As part of Oracle’s ongoing commitment to open source in general, and to Kubernetes and the Cloud Native Computing Foundation specifically, Oracle has open sourced the Operator and is committed to enhancing it with additional features. Oracle welcomes feedback, issues, pull requests, and feature requests from the WebLogic community.
21
24
@@ -155,11 +158,18 @@ Please refer to [Scaling a WebLogic cluster](site/scaling.md) for more informati
155
158
156
159
Please refer to [Shutting down a domain](site/shutdown-domain.md) for information about how to shut down a domain running in Kubernetes.
157
160
158
-
## Load balancing with the Traefik Ingress controller
161
+
## Load balancing
162
+
163
+
### Traefik
159
164
160
-
This release of the operator supports only the Traefik load balancer/Ingress controller. Support for other load balancers is planned in the future.
161
165
Please refer to [Load balancing with Traefik](site/traefik.md) for information about the current capabilities.
162
166
167
+
### Voyager
168
+
169
+
170
+
### Apache
171
+
172
+
163
173
[comment]: #(Exporting operator logs to ELK. The operator provides an option to export its log files to the ELK stack. Please refer to [ELK integration]site/elk.md for information about this capability.)
0 commit comments