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: site/scaling.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,8 +45,9 @@ When the operator receives a scaling request, it will:
45
45
* Validate that the specified domain, identified by `domainUID`, exists.
46
46
* Validate that the WebLogic cluster, identified by `clusterName`, exists.
47
47
* Verify that the specified WebLogic cluster has a sufficient number of configured servers to satisfy the scaling request.
48
-
* Initiate scaling by setting the `replicas` property within the corresponding domain custom resource either in:
49
-
* a `clusterStartup` entry, if defined within its cluster list.
50
-
* at the domain level, if not defined in a `clusterStartup` entry and the `startupControl` property is set to `AUTO`.
48
+
* Initiate scaling by setting the `replicas` property within the corresponding domain custom resource, which can be done in either:
49
+
50
+
* A `clusterStartup` entry, if defined within its cluster list
51
+
* At the domain level, if not defined in a `clusterStartup` entry and the `startupControl` property is set to `AUTO`
51
52
52
53
In response to a change to either `replicas` property, in the domain custom resource, the operator will increase or decrease the number of pods (Managed Servers) to match the desired replica count.
0 commit comments