helm-charts VS k3s-home-cluster

Before we can authenticate OpenSearch against Keycloak, we'll need to install Keycloak. The following Ansible snippet demonstrates how to deploy Keycloak onto a Kubernetes cluster using the codecentric helm chart.

HA Keycloak on top of Kubernetes https://github.com/codecentric/helm-charts/tree/master/charts/keycloak I dropped the chart db in favor of https://github.com/zalando/postgres-operator

Yeah this error suggests that the ingress is not correctly configured to forward the given information. Maybe take a look at some keycloak helm chart e.g. https://github.com/codecentric/helm-charts/blob/master/charts/keycloak/templates/ingress.yaml

Having experienced the issue of identity management in past projects (I've literally published 5 web apps which became some iteration of user-profile applications), I found Keycloak to be of particular use when it comes to managing users and federating accounts. Keycloak is an open-sourced enterprise service which manages identity, authentication, authorization, and account federation which is part of the JBoss project and backed by RedHat. Since I wanted to use the Keycloak helm chart the Keycloak service runs using a Postgres backend.

Yeah, it's not the easiest thing in the world to get up and running but not quite as hard as it might seem at first look. If you are already using k8s then you can use https://github.com/codecentric/helm-charts/tree/master/chart... to deploy Keycloak fairly easily. If you're not using k8s then it is probably more of an undertaking.

https://github.com/codecentric/helm-charts/tree/master/charts/keycloak#running-keycloak-behind-a-reverse-proxy

I published the cluster set-up into an Ansible playbook on GitHub