docs: Extend CRD reference in Keycloak documentation with custom image functionality #524
Conversation
This file contains 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
UtkarshUmre
force-pushed
the
UtkarshUmre-patch-1
branch
from
18b5c68 to
9071f61
Compare
pmig
force-pushed
the
UtkarshUmre-patch-1
branch
from
9071f61 to
5f740aa
Compare
pmig
approved these changes
Feb 27, 2024
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.
This pull request enhances the documentation for the Keycloak Custom Resource Definition (CRD) by incorporating details about custom image functionality. By doing so, it provides users with clear instructions on how to utilize custom Docker images effectively within Keycloak deployments. This documentation update addresses the need for comprehensive guidance, ensuring users can seamlessly integrate custom images into their Keycloak instances, thereby enhancing flexibility and customization options for Keycloak deployments.
fixes #462