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: documentation/4.0/content/managing-domains/domain-lifecycle/scaling.md
+4Lines changed: 4 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -228,6 +228,10 @@ operations on a cluster. These policies monitor one or more types of WebLogic Se
228
228
in a policy is met, the policy is triggered, and the corresponding scaling action is executed. The WebLogic Kubernetes Operator project provides a shell script, [`scalingAction.sh`](https://github.com/oracle/weblogic-kubernetes-operator/blob/{{< latestMinorVersion >}}/operator/scripts/scaling/scalingAction.sh),
229
229
for use as a Script Action, which illustrates how to issue a request to the operator’s REST endpoint.
230
230
231
+
{{% notice note %}}
232
+
Beginning with operator version 4.0.5, the operator's REST endpoint is disabled by default. Install the operator with the Helm install option `--set "enableRest=true"` to enable the REST endpoint.
233
+
{{% /notice %}}
234
+
231
235
##### Configure automatic scaling of WebLogic clusters in Kubernetes with WLDF
232
236
The following steps are provided as a guideline on how to configure a WLDF Policy and Script Action component for issuing scaling requests to the operator's REST endpoint:
Copy file name to clipboardExpand all lines: documentation/4.0/content/managing-operators/the-rest-api.md
+4Lines changed: 4 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -15,6 +15,10 @@ or for getting certain aspects of a domain's status (for example, instead of cal
15
15
You also can use the REST API as an alternative approach for initiating scaling operations
16
16
(instead of using the Kubernetes API or command line to alter a domain resource's `replicas` values).
17
17
18
+
{{% notice note %}}
19
+
Beginning with operator version 4.0.5, the operator's REST endpoint is disabled by default. Install the operator with the Helm install option `--set "enableRest=true"` to enable the REST endpoint.
20
+
{{% /notice %}}
21
+
18
22
### Configure the operator's external REST HTTPS interface
19
23
20
24
The operator can expose an external REST HTTPS interface which can be accessed from outside the Kubernetes cluster. As with the operator's internal REST interface, the external REST interface requires an SSL/TLS certificate and private key that the operator will use as the identity of the external REST interface.
0 commit comments