> 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/encrypting-helm-chart-sensitive-data.md).
# Encrypting Helm chart sensitive data
Encrypting sensitive Sonar properties in SonarQube Server 2025.2.
You can encrypt any Sonar property stored in the `values.yaml` file and some Helm parameters, such as `jdbcPassword`, that will be managed as Sonar properties. The encryption algorithm used is AES with 256-bit keys.
You must have the Administer System permission in SonarQube Server to perform this procedure.
## Prerequisites
SonarQube Server must be up and running.
## Step 1: Create the encryption key
1. In SonarQube Server UI, go to **Administration > Configuration > Encryption**.
2. Select **Generate Secret Key**. An encryption key is generated.
3. Store the generated key in a safe location.
## Step 2: Create a Kubernetes secret to store the encryption key
Use the command below:
```css-79elbk
kubectl create secret generic --from-literal sonar-secret.txt=
```
Example:
```css-79elbk
kubectl create secret generic --from-literal sonar-secret.txt=EgycYJc4Ek4uj2pH39e3+bnnk15IrVu4dxtfjDyN1y8= myEncryptionKeySecret
```
## Step 3: Enable the encryption in the Helm chart
Install the encryption key secret as follows:
1\. Add the following to the `values.yaml` file:
```css-79elbk
sonarSecretKey:
```
2\. Use the helm upgrade command.
## Step 4: Encrypt the sensitive data
To encrypt a sensitive property in `values.yaml`:
1\. In SonarQube Server UI, go to **Administration > Configuration > Encryption**.
2\. Enter the value of the property.
3\. Select the **Encrypt** button. The encrypted value of the property is generated.
4\. Select the copy tool.
5\. In the `values.yaml` file, replace the value of the property with the copied encrypted value.
6\. Use the helm upgrade command.
---
# 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/encrypting-helm-chart-sensitive-data.md?ask=&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.