keycloak-operator | OpenShift Operator based on the Operator SDK | Identity Management library
kandi X-RAY | keycloak-operator Summary
kandi X-RAY | keycloak-operator Summary
An OpenShift Operator based on the Operator SDK for syncing resources in Keycloak.
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- Upgrade implements the Keycloak interface
- UpgradeDeploymentConfig is used to upgrade a deployment config
- The kubernetes client
- EnvVarsAndVolumeMountsUpgraded returns true if the deployment config has been upgraded
- NewTemplateProcessor returns a new TemplateProcessor
- GetInstallResources will build the install resources
- NewReconciler creates a new Reconciler
- get the template path
- GetInstallResourcesAsRuntimeObjects returns a list of runtime . Object
- newTemplateHelper creates a new MonitoringTemplateHelper
keycloak-operator Key Features
keycloak-operator Examples and Code Snippets
make test/unit
#build an image with enabled tests
make image/build/test
#push the operator image
docker push myimage
#run the test pod
make test/e2e
INFO[0000] Go Version: go1.10.2
INFO[0000] Go OS/Arch: darwin/amd64
INFO[0000] operator-sdk Version: 0.0.7
Community Discussions
Trending Discussions on keycloak-operator
QUESTION
I have a theme with a size >1MB (which precludes the configmap-solution provided as an answer to this question).
This theme has been been packaged according to the Server Development Guide - its folder structure is
...ANSWER
Answered 2021-Dec-27 at 19:23As is so often the case, an uncaught typo was the source of the error.
The directory-structure must not be
- META-INF/keycloak-themes.json
- themes/[theme-name]/[theme-role]/theme.properties
- [...]
But instead
- META-INF/keycloak-themes.json
- theme/[theme-name]/[theme-role]/theme.properties
- [...]
Given a correct structure, keycloak-operator can successfully deploy and load custom-themes as jar-extensions.
QUESTION
I just installed the keycloak kubernetes operator using the official OperatorHub.io guide: https://operatorhub.io/operator/keycloak-operator
Afterwards I created an operator deployment by following the official keycloak getting started guide: https://www.keycloak.org/getting-started/getting-started-operator-kubernetes
I can see that everything works out as the needed pods, the service and the ingress are coming up and are running after a small amount of time. What I don't understand is how to access the ingress created by the deployment as the spec does not specify the normal host of my kubernetes cluster, but this instead:
...ANSWER
Answered 2021-Jul-05 at 15:43You have configured the following in your Keycloak CRD.
QUESTION
I was installing Keycloak using Operator (version 13.0.0). The updated code has theme related stuff github repository and supports custom theme integration quite well. All we need an URL where the custom theme
is located. I tried it and worked flawlessly.
However, what if we have themes in some local directory, not on some public URL. How do we suppose to upload the theme
in the Keycloak then?
I've tried using the File URL and file paths as well but didn't work for me.
The Keycloak.yaml
ANSWER
Answered 2021-May-18 at 18:49You can create a .tar file (e.g., custom_theme.tar) with the custom themes to be used in Keycloak, and then mount a volume to the folder where the Keycloak themes are stored (i.e., /opt/jboss/keycloak/themes/my_custom_theme
), and copy the .tar file with the custom themes from a local folder into the Keycloak container.
You can find complete example of this approach here.
QUESTION
I installed Keycloak using Operator (version 12.0.1). It's using the repository github repository Everything worked seamlessly. A keycloak instance has been launched and I could log in using admin credentials. I could see a realm, clients, users, etc working as expected.
But I do have a custom theme that I want to use it. For that, I make the following changes in my-realm.yaml.
...ANSWER
Answered 2021-Jan-27 at 16:43But, I didn't see any of the themes in my realms/my-realm/theme-settings. I can see only the default theme in the select box (i.e. keycloak, base). I am expecting account-theme, admin-theme, email-theme, login-theme in their respective select boxes.
The problem is/was that -- until yesterday the 26th of January of 2021, commit f2d0370290d6abe91724b2536748aa6b1245d1e1 (pull request #284) -- by default the Keycloak Operator did not recognize the Theme-related fields (i.e., accountTheme
, adminTheme
, emailTheme
, loginTheme
).
This feature was not deployed on the current latest release (12.0.2), however it is available of master. So you can go from there.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install keycloak-operator
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page