-
Notifications
You must be signed in to change notification settings - Fork 8.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[bitnami/keycloak] Guidance on how to automate realm backup for Keycloak #25025
Comments
By adding an Yaml:
Logs:
Demonstration that realm exists:
I suspect this indicates that the separate Pod is not connecting to the same Keycloak datasource - but I don't know how to configure it to do so. |
I was able to get a separate Pod to export Keycloak realms by adding a |
Hi! Thank you so much for sharing your tests! The community will benefit from this. Let's see what the upstream devs say so we can improve the README.md file |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
Name and Version
bitnami/keycloak:19.3.4
What is the problem this feature will solve?
Exporting realms provides resiliency against persistence failures, and allows an application to be "cold-started" from configuration rather than having to be manually initialized
What is the feature you are proposing to solve the problem?
Documentation on the recommended process to carry out realm exports automatically
What alternatives have you considered?
cron
to runkc.sh export
from the Keycloak container.cron
is not installed on the custom image (and installing new software is not possible), so this is not feasibleCronJob
to run the backup. Other pods do not seem to be fully configured to be able to backup the application's data - the following Job:resulted in the following logs:
The text was updated successfully, but these errors were encountered: