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.

Tip: You can verify the status of the extension by running the kubectl get pods -n {name_of_the_namespace} command. The status of an enabled server extension is displayed as Running.

About this task

You must substitute {my-rtas} 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

  1. Log in to the platform that you used to install the server software.

    For example, you can log in to the OpenShift Container Platform (OCP) cluster if you installed the server software on Red Hat OpenShift.

  2. Run the following command to disable all the extensions: 
    helm upgrade {my-rtas} -n test-system ./ibm-rtas-prod \
--reuse-values \
--set global.ibmRtasJmeterEnabled=false \
--set global.ibmRtasJunitEnabled=false \
--set global.ibmRtasCodesweepEnabled=false\
--set global.ibmRtasPostmanEnabled=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-rtas} -n test-system ./ibm-rtas-prod \
--reuse-values \
--set global.ibmRtasJmeterEnabled=false
  3. 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.

Results

You have disabled the required server extensions on Rational® Test Automation Server.