> 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/2025.2/setup-and-update/deploy-on-kubernetes/server/introduction.md).

# Introduction

Main steps for installing SonarQube Server 2025.2 on Kubernetes or Openshift.

This section explains how to install SonarQube Server on Kubernetes or OpenShift (see also the [Helmchart documentation](https://artifacthub.io/packages/helm/sonarqube/sonarqube#cpu-and-memory-settings)). It does not apply to Data Center Edition. For the latter, see [Introduction](/sonarqube-server/2025.2/setup-and-update/deploy-on-kubernetes/dce/introduction.md) to Data Center Edition for more information.

{% hint style="info" %}
Your feedback is welcome at [our community forum](https://community.sonarsource.com/).
{% endhint %}

To deploy the SonarQube Server on Kubernetes or OpenShift:

1. Read [Before you start](/sonarqube-server/2025.2/setup-and-update/deploy-on-kubernetes/server/before-you-start.md).
2. Customize the SonarQube Server Helm chart. See [Customizing Helm chart](/sonarqube-server/2025.2/setup-and-update/deploy-on-kubernetes/server/customizing-helm-chart.md).
3. Install the Helm chart. See [Installing Helm chart](/sonarqube-server/2025.2/setup-and-update/deploy-on-kubernetes/server/installing-helm-chart.md).
4. 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 analyzing source code. See [Project analysis setup](/sonarqube-server/2025.2/analyzing-source-code/overview.md).
5. If necessary, encrypt helm chart sensitive data. See [Encrypting Helm chart sensitive data](/sonarqube-server/2025.2/setup-and-update/deploy-on-kubernetes/encrypting-helm-chart-sensitive-data.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/2025.2/setup-and-update/deploy-on-kubernetes/server/introduction.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.