Keycloak Helm chart Install for Kubernetes

Configuring the server
1

Hi Guys,
New to Keycloak , wanted to know if there is a helm chart based deployment present for keycloak that can be deployed to a kubernetes cluster ? I did’nt find any installation via Helm chart under keycloak Documentation.

2

There is no official Helm chart from the Keycloak project itself. Only a K8s operator is available.

codecentric offers a very well maintained and customizable Helm chart at their GitHub account: helm-charts/charts/keycloakx at master · codecentric/helm-charts · GitHub

3

Thanks for info , what about Bitnami , i see they also have keycloak helm chart? Basically we are looking to run keycloak at Production grade on GKE clusters . Any suggestions for which one to choose ?

Also whats the difference between codecentric keycloak and keycloakx charts?

4

The keycloakx chart is for the Quarkus based distribution, since it needs other parameter at runtime.

5

Hey guys , what is the latest version that codecentirc deploys keycloak with . I see we have version 23+ in Keycloak . But the chart references version 17-legacy

1 Like
6

See answer above your question and Codecentric vs bitnami, - #6 by dasniko

7

Hi, have you managed to get a char version that works with keycloak version24x?

8

None of the suggestions changed?

EIther the codecentric keycloakx chart or the bitnami chart.

Take a look at the repositories, at the issues, at the pull requests and make a decision which is in a better maintenance state.

9

Keycloak Deployment Strategy for Production: Operator vs Helm in Production Environments

With Keycloak’s incubation into the CNCF, many organizations are deploying it on Kubernetes. While the Operator offers advanced capabilities, we’ve observed that most teams still prefer the simplicity of Helm charts for deployment. This raises an important question: is there a roadmap for an official Helm chart directly from the Keycloak project?

The current dependency on third-party charts (Bitnami, Codecentric) introduces strategic risk due to:

  1. Corporate acquisitions affecting these maintainers

  2. Shifting business models that may impact licensing and support

  3. Potential divergence from the upstream Keycloak roadmap

These factors suggest these third-party options may not provide the stability needed for long-term production deployments.

What recommendations do you have for organizations standardizing on Keycloak in Kubernetes environments who require both operational simplicity and long-term sustainability in their deployment approach?