Repository navigation
Replies: 1 comment 1 reply
|
@absynth76 Hello, thank you for the suggestion. The new Operator lives inside the main Keycloak repository due to its tight integration with the server. You can filter out any issues related to the Operator using labels. The repository with the legacy Operator will be archived after Keycloak 20 is released. |
1 reply
|
Where can we find instruction or Custom Resources for the quarkus Operator? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
For clarity purpose, about issues, discussions and so on, maintainability would be better if keycloak operator would be located in a dedicated repository.
In that matter, why not have keep the current keycloak-operator repository, using another branch, until it's final ?
example, there are more than 1000 issues logged on keycloak repository, it's really hard or even impossible to distinguish the one that are operator related only.
All reactions