Disabling the MCP Deployment in DevOps Velocity
You can disable the MCP deployment in the HCL DevOps Velocity (Velocity) to minimize resource consumption if the MCP server is not in use. By default, the MCP deployment is enabled. The MCP deployment is enabled with the default configuration.
Before you begin
You must have completed the following tasks:
- Gained access to the Kubernetes cluster where Velocity is deployed.
- Installed and configured Helm.
- Installed Velocity application using a Helm chart.
About this task
In Velocity, MCP is deployed as a Kubernetes Deployment. You can disable the MCP component by updating the Helm values configuration and upgrading the release.
Procedure
-
Open the
values.yamlfile used for installing Velocity. - Locate the MCP configuration parameter.
-
Set the MCP enablement flag to
false.mcpEnabled:false -
Upgrade the Velocity Helm
release using existing values.
helm upgrade <release_name> -n <custom_namespace_name> \ ./accelerate-<version>-helm.tgz \ --set license=accept \ --reuse-values -f values.yaml -
Verify that the MCP deployment has been removed.
kubectl get deployments -
Confirm that the MCP pod is no longer running.
kubectl get pods
Results
You have disabled the MCP deployment in Velocity, and the corresponding pod is no longer running in the cluster.