An RWS WM specific Keycloak Helm Chart

This chart makes it possible to deploy Keycloak on RWS infrastructure.

It uses the keycloak operator to deploy the basic keycloak instance.

For the persistence, it relies on the external-postgres chart to provide a secret for an existing databsee or a database hotel managed database.

This helm chart is a clone of code used for the deployment of the central Keycloak instances for RWS Water Management

Special notes on this release

This project is provided as an open source copy of our custom helmchart. It expects some middleware on top of plain kubernetes to work. This is up to the implementer to address.

• The chart does not manage its own postgres database. It needs to be supplied and credentials to this database need to be provided to the keycloak custom resource. We rely on internal service that provides databases dynamicly. This proces also creates a secret in the target namespace with we map. But you need to come up with your own solution for this.
• We rely on the external secrets operator and we use Hashicorp Vault as an external backing for these secrets. OpenBao may work too, we haven't tested this.
• We deploy some keycloak dashboards to Grafana using configmaps. This may or may not work for you. We recommend looking at using the Grafana operator for this.
• We use a custom TLS trust bundle so that the internal PKI signed certificates work ok.

Questions regarding this code can be sent to et@rws.nl which we will answer on a best effort basis.

Values

Possible values you can override and configure for the Keycloak deployment can be found in the values.yaml file. These values allow you to customize the deployment according to your specific requirements.