Disabling server extensions and features
When you do not want the server extensions to run on the cluster to save server resources or when you no longer want to use the test authoring feature, you can disable them.
Before you begin
You must have ensured that the server extension or the test authoring feature that you want to disable is enabled and running.
Note: You can verify the status by running the kubectl get pods -n test-system
command. The status of an enabled server extension is displayed as
Running.
About this task
{my-ots}
with the
release name that you provided during the installation of the server software in the
following procedure.Procedure
- Log in to the Ubuntu server using an SSH session.
-
Run the following command to disable the test authoring feature:
helm upgrade {my-ots} -n test-system ./hcl-onetest-server \ --reuse-values \ --set global.hclOneTestAuthorEnabled=false
-
Run the following command to disable all the extensions:
helm upgrade {my-ots} -n test-system ./hcl-onetest-server \ --reuse-values \ --set global.hclOneTestPostmanEnabled=false \ --set global.hclOneTestJMeterEnabled=false \ --set global.hclOneTestJUnitEnabled=false
If you want to disable any specific extension, then you can set the respective helm parameter value to false. For example, to disable the JMeter extension alone, then you can run the following command:
helm upgrade {my-ots} -n test-system ./hcl-onetest-server \ --reuse-values \ --set global.hclOneTestJMeterEnabled=false
-
Run the following command to verify the status of the extensions or the test
authoring feature:
kubectl get pods -n test-system
Note: The pod for each server extension that you disabled no longer displays.