CH-159 Keycloak upgrade configuration changes#800
Merged
Conversation
filippomc
reviewed
May 6, 2025
filippomc
reviewed
May 6, 2025
filippomc
reviewed
May 6, 2025
filippomc
approved these changes
May 23, 2025
Collaborator
filippomc
left a comment
There was a problem hiding this comment.
Tested and works well. Requires more documentation on the update process, expecting that in a later PR
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes CH-159
Implemented solution
Update Keycloak to 26.2.1
Update events plugin configuration
Adjust template settings to ensure compatibility with new version of Kafka
How to test this PR
Create a typical application using harness-application then prepare deployment using harness-deployment. Deploy to a k8s instance and all KC related components should work as expected alongside KC 26.2.1.
Sanity checks:
Breaking changes (select one):
breaking-changeand the migration procedure is well described abovePossible deployment updates issues (select one):
alert:deploymentTest coverage (select one):
Documentation (select one):
Nice to have (if relevant):