> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-server/server-installation/ai-agents/customizing-helm-chart.md).

# Deploying with the Helm chart

Enable the Agent Orchestrator, the agent runtimes, Vortex analysis, and the gVisor sandbox in the SonarQube Server Helm chart. This page is for SonarQube Server 2026.5.

The AI agent components ship as part of the SonarQube Server Helm chart, turned off by default. Enable the components you need and provide their configuration, either in `values.yaml` or with `--set` on the command line. Values passed on the command line take precedence.

Install the chart the usual way once you've set these values, see [Installing Helm chart](/sonarqube-server/server-installation/on-kubernetes-or-openshift/installing-helm-chart.md).

{% hint style="info" %}
See [Before you start](/sonarqube-server/server-installation/ai-agents/before-you-start.md), and complete [Setting up the sandbox runtime](/sonarqube-server/server-installation/ai-agents/sandbox-runtime.md) and [Setting up shared storage](/sonarqube-server/server-installation/ai-agents/shared-storage.md), first. The chart validates the combination of values you set and refuses to install if a component is missing a dependency.
{% endhint %}

## Enabling the agentic features <a href="#agentic-features" id="agentic-features"></a>

The Helm chart repository documents every value for the Agent Orchestrator, the Hunter Agent and Remediation Agent runtimes, Vortex analysis, and the gVisor sandbox, along with their prerequisites, network egress rules, and autoscaling options:

* [Agentic features](https://github.com/SonarSource/helm-chart-sonarqube/tree/master/charts/sonarqube#agentic-features) for Developer and Enterprise Edition
* [Agentic features](https://github.com/SonarSource/helm-chart-sonarqube/tree/master/charts/sonarqube-dce#agentic-features) for Data Center Edition

On OpenShift, the chart ignores the gVisor values and sandboxes the agent runtimes with Kata Containers instead. See [Setting up the sandbox runtime](/sonarqube-server/server-installation/ai-agents/sandbox-runtime.md#on-openshift).

## Next step <a href="#next-step" id="next-step"></a>

Confirm the deployment works, see [Verifying the deployment](/sonarqube-server/server-installation/ai-agents/verifying-the-deployment.md).

## Related pages <a href="#related-pages" id="related-pages"></a>

* [Installation overview](/sonarqube-server/server-installation/ai-agents/installation-overview.md)
* [Configuration reference](/sonarqube-server/server-installation/ai-agents/configuration-reference.md)
* [Verifying the deployment](/sonarqube-server/server-installation/ai-agents/verifying-the-deployment.md)
* [Customizing Helm chart](/sonarqube-server/server-installation/on-kubernetes-or-openshift/customizing-helm-chart.md)
* [Capacity planning](/sonarqube-server/server-installation/ai-agents/capacity-planning.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sonarsource.com/sonarqube-server/server-installation/ai-agents/customizing-helm-chart.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.