Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Remove built-in support for extensions in the operator #10835

Closed
vmuzikar opened this issue Mar 21, 2022 · 0 comments · Fixed by #10848
Closed

Remove built-in support for extensions in the operator #10835

vmuzikar opened this issue Mar 21, 2022 · 0 comments · Fixed by #10848
Assignees
@andreaTP
Labels
area/operator Keycloak.X Operator kind/eol
Milestone
18.0.0

Comments

@vmuzikar
Copy link
Contributor

The operator is designed to provide production grade deployments of Keycloak. It is a best practice that production grade deployments use a custom image if extensions are required.
Reasoning:

  • Keycloak will not start if the provider of the Jar (e.g. GitHub) is down or not reachable
  • Downloading something on the fly on start breaks a bunch of patterns regarding immutability and idempotency
  • Slow down Keycloak start with little benefit
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@andreaTP andreaTP

Labels
area/operator Keycloak.X Operator kind/eol
Projects
Keycloak.X: Operator
Status: Done ✅
Milestone
18.0.0
Development

Successfully merging a pull request may close this issue.

Remove extensions support from the operator CRD andreaTP/keycloak
2 participants
@andreaTP @vmuzikar