Skip to content

TRG 5.07: Add Keycloak to Cloudpirates chart dependency alignment #1571

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

Draft
Copilot wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

TRG 5.07: Add Keycloak to Cloudpirates chart dependency alignment #1571

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cc96230
Initial plan
Copilot Jul 31, 2026
193536c
Add Keycloak dependency alignment to TRG 5.07
Copilot Jul 31, 2026
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
21 changes: 20 additions & 1 deletion docs/release/trg-5/trg-5-07.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,14 +4,15 @@ title: TRG 5.07 - Chart Dependencies

| Status | Created | Post-History |
|--------|-------------|---------------------------------------------- |
| Update | 31-Jul-2026 | Add Keycloak dependency alignment |
| Update | 28-Oct-2023 | Migrate from Bitnami to Cloudpirates |
| Update | 20-Sep-2023 | Adjust PostgreSQL version |
| Active | 07-Mar-2023 | |
| Draft | 02-Dec-2022 | n/a |

## Why

Dependencies like a database (postgresql) are used across Eclipse Tractus-X. It's critical to align those common dependencies when those dependencies are later replaced with hosted versions, like the database. Single instance of these dependencies that can be shared among all products in the future.
Dependencies like a database (postgresql) or an identity provider (keycloak) are used across Eclipse Tractus-X. It's critical to align those common dependencies when those dependencies are later replaced with hosted versions, like the database. Single instance of these dependencies that can be shared among all products in the future.

## Description

Expand Down Expand Up @@ -52,3 +53,21 @@ The following table describes the required version of dependencies for all produ
| Name | Repo URL | Chart version | App version |
|----------|------------------------------------------------------------------|:-------------:|:-----------:|
| postgres | [Cloudpirates](https://registry-1.docker.io/cloudpirates) | 0.11.x | 18.x.x |
| keycloak | [Cloudpirates](https://registry-1.docker.io/cloudpirates) | 0.13.x | 26.x.x |

## Migrating from Bitnami to Cloudpirates

The Bitnami catalog for the affected dependencies (e.g. PostgreSQL, Keycloak) is being deprecated, so products
should migrate to the Cloudpirates charts referenced above. A generic migration guide and a concrete example
are available to support this transition:

- Generic guide: [GENERIC_BITNAMI_TO_CLOUDPIRATES_KEYCLOAK_MIGRATION_GUIDE.md](https://github.com/eclipse-tractusx/tutorial-resources/blob/main/migration-guides/GENERIC_BITNAMI_TO_CLOUDPIRATES_KEYCLOAK_MIGRATION_GUIDE.md)
- Reference implementation (Industry Core Hub): [BITNAMI_TO_CLOUDPIRATES_KEYCLOAK_MIGRATION_GUIDE.md](https://github.com/eclipse-tractusx/industry-core-hub/blob/main/docs/migration-guides/BITNAMI_TO_CLOUDPIRATES_KEYCLOAK_MIGRATION_GUIDE.md)

:::caution token format changes between Keycloak versions

When upgrading Keycloak across several major versions (e.g. from 22.x to 26.x), be aware of changes in the
issued token format. Verify that all clients and services consuming the tokens are compatible with the target
version before rolling out the migration.

:::