Scale an Oracle SOA Suite Domain

With the Oracle SOA Suite Domain deployed, you can now scale the number of managed servers in the SOA cluster. There are two ways to do so: editing the values in the Helm chart (our recommended method) or editing the domain manifest directly (which we don't recommend).

Option 1: Scale by Editing the Domain Manifest

The original way of scaling the Oracle SOA domain when deploying Kubernetes manifests manually is to edit the domain manifest. We don't recommend this method because the changes are no longer tracked by the Helm deployment.

Edit the manifest with kubectl (assuming the deployment name and namespace were kept as defaults)
```
kubectl edit domain mysoa -n soans
```
This opens a vim editor where you can see the content of the domain definition. Scroll down to the section:
```
clusters:
- clusterName: soa_cluster
  replicas: 2
```
Press the i key to enter vim's edit mode.
Change the number of replicas to 3.
Press the ESC key to exit the edit mode
Type :wq (colon w q) to write the changes and quit the editor.
Observe the change in the number of managed servers by entering:
```
kubectl get pods -n soans
```
It should show a new entry:
```
mysoa-soa-server3   0/1     ContainerCreating   0          6s      <none>      10.0.10.56    <none>           <none>
```

Option 2: Scale by Updating the Helm Chart

To properly track the changes through Helm, we recommend that you scale the number of managed servers by editing the chart input values.

In this option, we scale the number of managed servers for the OSB cluster this time and observe how the Helm controller returns the SOA cluster to its original number of managed servers.

Update the Helm Chart:

helm upgrade mysoa oracle/soa-suite \
  -n soans \
  --reuse-values \
  --set domain.osbCluster.managedServers.count=3

Check the effect of the change. Enter:
```
kubectl get pods -n soans
```
to list the changes. You should see the following:
```
mysoa-soa-server3   0/1     Terminating         0          6s      <none>      10.0.10.56    <none>           <none>
mysoa-osb-server3   0/1     ContainerCreating   0          30s     10.1.0.134   10.0.10.56   <none>           <none>
```
The number of replicas for the SOA cluster known to Helm was two, so our previous change to three is overridden and changed back to two, causing the mysoa-soa-server3 to be terminated, while the change we just made in the values created a new managed server for the OSB cluster, named mysoa-osb-server3.