You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Keycloak is an open source software product to allow single sign-on with identity and access management aimed at modern
applications and services. It supports various protocols such as OpenID, OAuth version 2.0 and SAML and provides
features such as user management, two-factor authentication, permissions and roles management, creating token services,
etc. The Keycloak Operator will allow you to deploy dedicated
instances of Keycloak at will using the newly registered
KeycloakCustomResourceDefinition.
Unfortunately the Keycloak Project does not provide a way to install
the Operator via a Helm Chart,
thus making it challenging to manage. This Helm Chart is built from the
official upstream sources
and closely tracks these for changes. It delivers all of these features within a single Docker image available
on quay.io.
This chart bootstraps a
Keycloak Operator Deployment on
a Kubernetes cluster using the Helm package manager. For cluster networking
a Service manifest is also created.
The chart creates the RBAC roles (ClusterRoles)
keycloakrealmimportcontroller-cluster-role, keycloakcontroller-cluster-role and (Roles) keycloak-operator-role.
These are enabled by default.
The chart supports configuring the Kubernetes manifests created for the Operator, however modifications are somewhat
discouraged, since the official release for vanilla Kubernetes uses static manifests. The Operator itself does not offer
any sort of configuration (to my knowledge). I will try to ensure the chart always matches
the upstream deployment at the given versions.
After deployment the Operator gives you access to the Keycloak CR making the deployment of Keycloak (even as a
cluster) as simple as: