B Advanced Configuration with OAA Override File

The OAA Override file is used to determine the number of each type of container that is started. By default, the installation starts one pod for each container, with predefined memory and CPU requirements. For a sandbox architecture is it not usually required to change these defaults. In a highly available production deployment, there should be a minimum of two for each container type.

If you need to change the number of containers to be started, enter the management container, for example:
kubectl exec -n oaans -ti oaamgmt-oaa-mgmt-84955fdf8f-x22k4 -- /bin/bash
and update the /u01/oracle/scripts/settings/oaaoverride.yaml file to increase the replicaCount for each type of container to the required quantity.

You can also use this file to specify the CPU and memory requirements. By declaring resource requirements, you ensure that a particular OAA pod is started only on a worker node that has sufficient capacity to service a pod with these resource requirements.

The following shows an example oaaoverride.yaml. You can change, add, or remove parameters based on your requirements:
#override file for oaa installation
 
#if database is external to the cluster set the flag to ExternalName
riskdb:
  service:
    type: ExternalName
 
#replica count of oaa service
replicaCount: 2
 
#The following properties define the dependency spui service and can be overridden here.
spui:
  resources:
    requests:
      cpu: 200m
      memory: "1Gi"
  replicaCount: 2
 
#The following properties define the dependency totp service and can be overridden here.
totp:
  resources:
    requests:
      cpu: 200m
      memory: "1Gi"
  replicaCount: 2
 
#The following properties define the dependency yotp service and can be overridden here.
yotp:
  resources:
    requests:
      cpu: 200m
      memory: "1Gi"
  replicaCount: 2
 
#The following properties define the dependency fido service and can be overridden here.
fido:
  resources:
    requests:
      cpu: 200m
      memory: "1Gi"
  replicaCount: 2
 
#The following properties define the dependency oaa-admin-ui service and can be overridden here.
oaa-admin-ui:
  resources:
    requests:
      cpu: 200m
      memory: "1Gi"
  replicaCount: 2
 
#The following properties define the dependency email service and can be overridden here.
email:
  resources:
    requests:
      cpu: 200m
      memory: "1Gi"
  replicaCount: 2
 
#The following properties define the dependency push service and can be overridden here.
push:
  resources:
    requests:
      cpu: 200m
      memory: "1Gi"
  replicaCount: 2
 
#The following properties define the dependency sms service and can be overridden here.
sms:
  resources:
    requests:
      cpu: 200m
      memory: "1Gi"
  replicaCount: 2
  
#The following properties define the dependency oaa-policy service and can be overridden here.
oaa-policy:
  resources:
    requests:
      cpu: 200m
      memory: "1Gi"
  replicaCount: 2
 
#The following properties define the defaults of risk and riskcc services.
risk:
  resources:
    requests:
      cpu: 200m
      memory: "1Gi"
  replicaCount: 2
 
riskcc:
  resources:
    requests:
      cpu: 200m
      memory: "1Gi"
  replicaCount: 2
#
#The following properties define the defaults of customfactor service.
customfactor:
  resources:
    requests:
      cpu: 200m
      memory: "1Gi"
  replicaCount: 2
#
#The following properties define the defaults of oaa-kba service.
oaa-kba:
  resources:
    requests:
      cpu: 200m
      memory: "1Gi"
  replicaCount: 2
 
#
#The following properties define the defaults of oaa-drss service.
oaa-drss:
  resources:
    requests:
      cpu: 200m
      memory: "1Gi"
  replicaCount: 2
For the deployment to use this file, you must enter the management container, and update the /u01/oracle/scripts/settings/installOAA.properties by uncommenting the following parameter:
common.deployment.overridefile=/u01/oracle/scripts/settings/oaaoverride.yaml
To update the deployment, run the following commands:
cd ~
OAA.sh -f installOAA.properties