Additional Helm parameters

You can find the information about Helm parameters that you can use during the installation of HCL DevOps Test Hub (Test Hub).

As a system administrator when you install or upgrade Test Hub, you can pass values for some of the individual parameters by using --set. The following table lists such parameters that you can use while running the helm install or helm upgrade command to enable or disable certain features in Test Hub.

Parameters Values Description

keycloak.signup.enabled

true

false

Use this parameter to show or hide the Sign-Up link on the Test Hub Login page.

The default value of the keycloak.signup.enabled parameter is set to false to enhance the security of Test Hub.

Note: You can use this parameter only during the installation of Test Hub.

If you have administrator access to Keycloak, then you can also enable the self-registration by using the Keycloak UI after the installation of Test Hub is complete. For more information, refer to the Keycloak documentation.

router.allowedOrigin

IP address or domain name of other servers.

Use this parameter to integrate call requests from other web servers to Test Hub.

The default configuration of Test Hub rejects all Cross-origin resource sharing (CORS). Therefore, you must use the router.allowedOrigin parameter to restrict CORS to a specific whitelist.

For example,
--set router.allowedOrigin=http://http.example.com:*,https://https.mydomain.net:*
Where, http.example.com and https.mydomain.net are the domains that you want to provide access to Test Hub.

You can also provide the value of router.allowedOrigin as the IP address when you cannot resolve a specific Domain Name Server (DNS). If your domain can be accessible through IP address on a specific port, then you can provide the value of router.allowedOrigin as follows:

--set router.allowedOrigin=*://ip-address:*,*://ip-address:port_number
For example, 
--set router.allowedOrigin="*://192.0.2.0:*"
--set router.allowedOrigin="*://192.0.2.1:3000"
Note: You can provide multiple domain names or IP addresses separated by a comma (,).

networkPolicy.egress.enabled

true

false

Set this parameter value to true to restrict traffic from Test Hub to private IP addresses.

The default configuration of Test Hub does not create any Egress policy to restrict the other endpoints that can connect with Test Hub. Therefore, you must use the networkPolicy.egress.enabled parameter to enable the Egress policy that can restrict traffic to private IP addresses.

For example,
--set networkPolicy.egress.enabled=true
You can inspect the deployed policy by running the following command:
kubectl get networkpolicy -n {namespace} {{main}}-allow-egress -oyaml
Note: You must substitute {namespace} with the name of the namespace and {{main}} with the release name that you used during the installation of Test Hub.

execution.template.

resources.limits.memory

 <size_of_memory>Gi

Use this parameter to run VU schedules that contain multiple Web UI tests or a large number of virtual users or a combination of Web UI, performance, and API tests.

The default value of the execution.template.resources.limits.memory parameter is set to 3Gi.

For example,
--set execution.template.resources.limits.memory=5Gi