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
I might have needed to kill a previously running pod. After that Keycloak started on the ARM pod.
Next steps:
See what happens if we only have ARM workers in our cluster. Which services start? Do we then still need the schedule settings for Keycloak?
We are building the image with the JDBC driver for AWS. How can we build such an image for ARM? Maybe adding a node selector for the build might be required to force the node - if source-to-image supports that.
nodeSelector
kubernetes.io/arch: arm64
ahus1
changed the title
Use ARM architecture to run Keycloak
Use ARM architecture to run Keycloak on OpenShift
Jul 30, 2024
Description
OpenShift with hosted control planes now supports ARM workers. Using such workers would be in-line with our company strategy.
Discussion
No response
Motivation
Save cloud costs both for us and our users
Details
No response
The text was updated successfully, but these errors were encountered: