Persistent keycloak #4
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Keycloak data and configurations are stored in Postgres (studiodb for semplicity), so if you restart, remove, and recreate Keycloak (or even the database itself), the configurations remain permanent.
Test:
https://skupper-x-vb-skupper-x-2.skupper-0-153f1de160110098c1928a6c05e19444-0000.us-east.containers.appdomain.cloud
user: myskupper and pass: skupper
Other config:

Two new Realm roles were created: van-owner and backbone-admin, then applied to the user myskypper (no need to set the admin role).
Improvements:
Maybe we can to set up a script like this to get the credential locally and set the yaml to read env vars: