> 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/data-center-edition/on-kubernetes-or-openshift/overview.md).

# Installation overview

Your entry point to deploy the Data Center Edition (DCE) on Kubernetes or OpenShift in SonarQube Server 2026.5.

As a DCE subscriber, Sonar will assist with the setup and configuration of your cluster. Get in touch with your account manager to receive appropriate onboarding resources.

This section explains how to install Data Center Edition on Kubernetes or OpenShift (see also the [SonarQube Server Helm chart documentation](https://artifacthub.io/packages/helm/sonarqube/sonarqube-dce)).

To deploy Data Center Edition on Kubernetes or OpenShift:

1. Read [Before you start](/sonarqube-server/server-installation/data-center-edition/on-kubernetes-or-openshift/before-you-start.md).
2. Customize the Helm chart and install it in Kubernetes. See:

   1. [Customizing the Helm chart](/sonarqube-server/server-installation/data-center-edition/on-kubernetes-or-openshift/customizing-helm-chart.md)
   2. [Installing the DCE Helm chart](/sonarqube-server/server-installation/data-center-edition/on-kubernetes-or-openshift/installing-from-helm-repo.md)

   Alternatively, if you want to deploy from the Google Cloud Platform, see [Installing from Google Cloud Platform](/sonarqube-server/server-installation/data-center-edition/on-kubernetes-or-openshift/installing-from-gcp.md).
3. Once your SonarQube Server is installed and running, you can access SonarQube Server UI in your web browser (the default system administrator credentials are **admin**/**admin**) and you’re ready to begin [Project analysis setup](/sonarqube-server/analyzing-source-code/overview.md).
4. If you have customized your Helm chart, you can now encrypt sensitive data in your `values.yaml` file. See [Encrypting sensitive data](/sonarqube-server/server-installation/on-kubernetes-or-openshift/encrypting-helm-chart-sensitive-data.md).

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

The agentic features are optional, require a separate subscription for each agent, and are enabled through the Helm chart. See [Deploying with the Helm chart](/sonarqube-server/server-installation/ai-agents/customizing-helm-chart.md).

{% hint style="warning" %}
On OpenShift, the agent runtimes are sandboxed with Kata Containers instead of gVisor, which is not available there. This requires the OpenShift sandboxed containers operator. See [Before you start](/sonarqube-server/server-installation/ai-agents/before-you-start.md) for the other requirements.
{% endhint %}


---

# 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/data-center-edition/on-kubernetes-or-openshift/overview.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.