Repository navigation
Replies: 5 comments 2 replies
|
Thank you for opening the issue. Keycloak already provides a container image, and if something is missing from that one, please open issues for individual features. There is already a discussion in #37636 to provide an Helm chart based on the KC Operator. Please join that discussion, and let us know if this covers your needs, and why it might not. There might be other community options deploy Keycloak's standard image, for example https://github.com/codecentric/helm-charts For now, as this issue seems to be a duplicate. Please discuss. |
|
Converted to a discussion before we create any associated epics / issues.
@joaocc the request here seems to be to maintain exactly what bitnami was providing. We are highly unlikely to do that as part of the core project. I'm not sure there would be sufficient justification for placing such an effort under a new repo in the keycloak organization. If the interested community members could agree on a non-keycloak repo location, we can certainly provide a pointer the site via our extensions page https://www.keycloak.org/extensions |
|
Please also see #37636 (comment) for some additional explanation on the need. |
Uh oh!
There was an error while loading. Please reload this page.
Description
As many of you already know, bitnami will stop supporting free charts and images on 2025-08-28.
It seems keycloak will not be supported in the bitnamicsecure images (the ones with only latest tag).
Has anyone discussed the possibility of hosting the bitnami/keycloak chart in this github org (copying the latest version, which seems to be chart v25.2.0, with keycloak v26.3.3 and keycloak-config-cli v6.4.0)?
This would allow us to use ghcr to host at least the help chart here?
I'm aware there are other issues concerned with deploying keycloak via operator, many people are using the deployment via keycloak-config-cli (the mechanism supported by bitnami). The bitnami image used in this chart has slightly different ways to configure keycloak, so replacing that image by the standard one is unlikely to work.
Discussion
No response
Motivation
Bitnami announcement that, after 2025-08-26, they will stop supporting or publishing images and chart, with some exceptions (that don't include keycloak) and that support will be moved to commercial subscription starting at 50k$.
After 2025-08-28, bitnami helm chart for keycloak will stop working (needs override to the docker image).
Details
Draft proposal.
Since bitnami repos are Apache licensed, this should be possible and should not have legal implications.
Naming could become keycloak-alt (since keycloak-bitnami could backfire) for both docker image and helm chart
Implement fixes that make the charts work without the bitnami infrastructure, but keeping the configuration settings structure.
Deploy the artifacts to ghcr under keycloak github account.
In the future, maintainers would have to be sought after for these versions.
All reactions