Disabling server extensions
When you do not want the server extensions to run on the cluster to save server resources, you can disable server extensions.
Before you begin
You must have ensured that the server extension that you want to disable is enabled and running.
About this task
{my-ots}
with the release name
that you provided during the installation of the server software in the following
procedure.The test-system is the name of the namespace. If you created a namespace by using a different value, then you must use that value in place of test-system in all the instances in this procedure.
Procedure
-
Log in to the platform that you used to install the server software.
For example, you can log in to the Ubuntu server using an SSH session if you installed the server software on Ubuntu.
-
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\ --set global.hclOneTestCodesweepEnabled=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:
kubectl get pods -n test-system
Note: The pod for each server extension that you disabled no longer displays.