Skip to content

Emphasize Management Identity #7026

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
+10 −8
Open

Emphasize Management Identity #7026

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0e2ec3c
Emphasize Management Identity
ingorichtsmeier Oct 10, 2025
5be99e0
Merge branch 'main' into external-postgres-management-identity
ingorichtsmeier Oct 16, 2025
b082696
Add to 8.8 after the release
ingorichtsmeier Oct 16, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions docs/self-managed/deployment/helm/configure/database/using-existing-postgres.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
id: using-existing-postgres
title: "Use external PostgreSQL"
sidebar_label: External PostgreSQL
description: "Learn how to use an Amazon OpenSearch Service instance in Camunda 8 Self-Managed deployment."
description: "Learn how to use an external PostgresQL instance in Camunda 8 Self-Managed deployment."
---

The [Helm chart deployment](/self-managed/deployment/helm/install/quick-install.md) can optionally install an internal PostgreSQL using [Bitnami subcharts](../../configure/registry-and-images/install-bitnami-enterprise-images.md). For production environments, we advise deploying PostgreSQL separately from the Camunda Helm charts. This guide steps through using an external PostgreSQL instance.
Expand All @@ -25,7 +25,7 @@ password: `examplePassword`
```SQL
CREATE DATABASE "web-modeler";
CREATE DATABASE "keycloak";
CREATE DATABASE "identity";
CREATE DATABASE "management-identity";
```

- **Kubernetes secrests:** Store the database password in a Kubernetes secret so it is not referenced in plain text within your values.yaml (This secret exists outside the Helm chart and will not be overwritten by subsequent helm upgrade commands). For example:
Expand All @@ -36,7 +36,7 @@ kubectl create secret generic camunda-psql-db --from-literal=password=examplePas

## Configuration

Three Camunda 8 Self-Managed components require PostgreSQL: Identity, Keycloak, and Web Modeler.
Three Camunda 8 Self-Managed components require PostgreSQL: Management Identity, Keycloak, and Web Modeler.
Each of these components must be configured to connect to the external PostgreSQL instance.

### Parameters
Expand Down Expand Up @@ -87,14 +87,15 @@ identity:
secret:
existingSecret: "camunda-psql-db"
existingSecretKey: "password"
database: "identity"
database: "management-identity"

identityKeycloak:
externalDatabase:
url: "jdbc:postgresql://db.example.com:5432/modeler"
user: "postgres"
existingSecret: "camunda-psql-db"
existingSecretKey: "password"
database: "keycloak"
auth:
adminUser: postgres
existingSecret: "camunda-psql-db"
Expand Down
9 changes: 5 additions & 4 deletions ...-8.8/self-managed/deployment/helm/configure/database/using-existing-postgres.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
id: using-existing-postgres
title: "Use external PostgreSQL"
sidebar_label: External PostgreSQL
description: "Learn how to use an Amazon OpenSearch Service instance in Camunda 8 Self-Managed deployment."
description: "Learn how to use an external PostgresQL instance in Camunda 8 Self-Managed deployment."
---

The [Helm chart deployment](/self-managed/deployment/helm/install/quick-install.md) can optionally install an internal PostgreSQL using [Bitnami subcharts](../../configure/registry-and-images/install-bitnami-enterprise-images.md). For production environments, we advise deploying PostgreSQL separately from the Camunda Helm charts. This guide steps through using an external PostgreSQL instance.
Expand All @@ -25,7 +25,7 @@ password: `examplePassword`
```SQL
CREATE DATABASE "web-modeler";
CREATE DATABASE "keycloak";
CREATE DATABASE "identity";
CREATE DATABASE "management-identity";
```

- **Kubernetes secrests:** Store the database password in a Kubernetes secret so it is not referenced in plain text within your values.yaml (This secret exists outside the Helm chart and will not be overwritten by subsequent helm upgrade commands). For example:
Expand All @@ -36,7 +36,7 @@ kubectl create secret generic camunda-psql-db --from-literal=password=examplePas

## Configuration

Three Camunda 8 Self-Managed components require PostgreSQL: Identity, Keycloak, and Web Modeler.
Three Camunda 8 Self-Managed components require PostgreSQL: Management Identity, Keycloak, and Web Modeler.
Each of these components must be configured to connect to the external PostgreSQL instance.

### Parameters
Expand Down Expand Up @@ -87,14 +87,15 @@ identity:
secret:
existingSecret: "camunda-psql-db"
existingSecretKey: "password"
database: "identity"
database: "management-identity"

identityKeycloak:
externalDatabase:
url: "jdbc:postgresql://db.example.com:5432/modeler"
user: "postgres"
existingSecret: "camunda-psql-db"
existingSecretKey: "password"
database: "keycloak"
auth:
adminUser: postgres
existingSecret: "camunda-psql-db"
Expand Down
Loading