이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 5. Using custom Red Hat build of Keycloak images
5.1. Red Hat build of Keycloak custom image with the Operator 링크 복사링크가 클립보드에 복사되었습니다!
With the Keycloak Custom Resource (CR), you can specify a custom container image for the Red Hat build of Keycloak server.
To ensure full compatibility of Operator and Operand, make sure that the version of Red Hat build of Keycloak release used in the custom image is aligned with the version of the operator.
5.1.1. Best practice 링크 복사링크가 클립보드에 복사되었습니다!
When using the default Red Hat build of Keycloak image, the server will perform a costly re-augmentation every time a Pod starts. To avoid this delay, you can provide a custom image with the augmentation built-in from the build time of the image.
With a custom image, you can also specify the Keycloak build-time configurations and extensions during the build of the container.
For instructions on how to build such an image, see Running Red Hat build of Keycloak in a container.
5.1.2. Providing a custom Red Hat build of Keycloak image 링크 복사링크가 클립보드에 복사되었습니다!
To provide a custom image, you define the image
field in the Keycloak CR as shown in this example:
With custom images, every build time option passed either through a dedicated field or the additionalOptions
is ignored.
5.1.3. Non-optimized custom image 링크 복사링크가 클립보드에 복사되었습니다!
While it is considered a best practice use a pre-augmented image, if you want to use a non-optimized custom image or build time properties with an augmented image that is still possible. You just need set the startOptimzed
field to false
as shown in this example:
Keep in mind this will incur the re-augmentation cost on every start.