I have set up an ELK cluster with OpenShift, including Elasticsearch in stateful mode and Kibana in a deployment. The issue I am facing is that we are using the free version of Elasticsearch, and I want to implement SSO, which is not possible with this version. Therefore, I have come up with the idea to set up a reverse proxy SSO with Nginx and Keycloak.
The problem that I faced is that in my OpenShift, I can’t use operators. What I did was pull the image from the Red Hat catalog and set up a PostgreSQL database. However, I don’t know what to do next or how it works, or which environment variables I should put in my deployment. I added KC_DB_USERNAME, KC_DB_PASSWORD, and KC_HOSTNAME, but the pod keeps failing.
i’m using this image :
Red Hat build of Keycloak image
this is the logs of the pod :
`Keycloak - Open Source Identity and Access Management
Find more information at: https://www.keycloak.org/docs/latest
Usage:
kc.sh [OPTIONS] [COMMAND]
Use this command-line tool to manage your Keycloak cluster.
Options:
-cf, --config-file <file>
Set the path to a configuration file. By default, configuration properties are
read from the "keycloak.conf" file in the "conf" directory.
-h, --help This help message.
-v, --verbose Print out error details when running this command.
-V, --version Show version information
Commands:
build Creates a new and optimized server image.
start Start the server.
start-dev Start the server in development mode.
export Export data from realms to a file or directory.
import Import data from a directory or a file.
show-config Print out the current configuration.
tools Utilities for use and interaction with the server.
completion Generate bash/zsh completion script for kc.sh.
Examples:
Start the server in development mode for local development or testing:
$ kc.sh start-dev
Building an optimized server runtime:
$ kc.sh build <OPTIONS>
Start the server in production mode:
$ kc.sh start <OPTIONS>
Enable auto-completion to bash/zsh:
$ source <(kc.sh tools completion)
Please, take a look at the documentation for more details before deploying in
production.
Use "kc.sh start --help" for the available options when starting the server.
Use "kc.sh <command> --help" for more information about other commands.`