Configurations

Helm is a standard tool used to manage Kubernetes applications, and the Helm chart defines how applications are deployed to Kubernetes. RIA Helm chart contains the default deployment configurations, which are specified in the values.yaml file.

Database

Add the database information that has been initialized. For more information, see Initialize Database.

global:
secretData: 
   DB_PASSWORD: "SOME_PASSWORD"
   DB_USERNAME: "SOME_USERNAME"
configmapData:
   DB_URL: "jdbc:postgresql://DB_SERVER:5432/DB_NAME

Helm initdb pre-install webhook

Our helm chart also supports on the fly initialization of database during installation. However, this would require you to provide a Super Admin credentials. The initdb will create the database, roles, schemas and load the data to the PostgreSQL server.


initDb:
  DB_SUPER_ADMIN_USER: "SOME_ADMIN_USER"
  DB_SUPER_ADMIN_PASSWORD: "SOME_ADMIN_PASSWORD"
  DB_HOST: "IP_OF_THE_SERVER"

Configure resources

Configure the volume size, resources limits, and resources requests. To configure these values, see Recommended Resources Configuration. The Test Automation is pre-configured with the following resource requests and limits:

Microservice	Replicas	CPU Requests (m)	Memory Requests (Mi)	CPU Limits (m)	Memory Limits (Mi)
fw-auth	1	1000	2000	1000	2000
fw-eureka	1	500	1000	500	1000
fw-fwssoui	1	100	100	100	100
fw-gateway	3	1000	2000	1000	2000
fw-notification	1	500	1000	500	1000
fw-ssologin	1	100	100	100	100
fw-tms	1	500	1000	500	1000
fw-tmsui	1	100	100	100	100
fw-ui	1	100	100	100	100
fw-utilities	1	500	1000	500	1000
ta-api-executor	1	1000	2000	1000	2000
ta-batch-executor	1	1000	2000	1000	2000
ta-core	1	1000	2000	1000	2000
ta-exec-dispatcher	1	1000	2000	1000	2000
ta-external-db	1	1000	2000	1000	2000
ta-ui	1	100	500	100	500
ta-ui-executor	1	1000	2000	1000	2000
kafka	3	1000	2000	2000	3000
hazelcast	3	500	1000	1000	2000

Update resources

To update the requests and limits of resources, add the following configuration under the parents.

ta:
  core:
    resources:
      requests:
        cpu: 200m
        memory: 500Mi

fw:
  gateway:                        
    resources:
      requests:
        cpu: 2000m
        memory: 2000Mi
      limits:
        cpu: 3000m

Disable resource management

ta:
  core:
    resources: {}

fw:
  gateway:
    resources: {}

Acces Test Automation

By default, the tool is exposed using nodeport on port 30000, so can access it via https://<hostname>:30000.

Enabling nginx ingress controller

fw:
  ssologin:
    ingress:
      enabled: true
      className: "nginx"
      annotations:
        nginx.ingress.kubernetes.io/proxy-body-size: 32m
        nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
      hosts:
        - host: 'ta.example.com'
          paths:
            - path: /
              pathType: Prefix
              backend:
              service:
                name: fw-ssologin
                port:
                  number: 8443
    tls:
      - secretName: subdomain-certificate
        hosts:
         - 'ta.example.com'