We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
The keycloak-realm-operator uses a sync period of five Minutes (see https://github.com/keycloak/keycloak-realm-operator/blob/main/cmd/manager/main.go#L108). This causes a massive load on the Kuberntes and Keycloak APIs, leading to throttling and an overall sloweness of the operator (when using many resources).
The default sync period is ten hours, and you should
Change this value only if you know what you are doing.
(see https://github.com/kubernetes-sigs/controller-runtime/blob/685db561ba77cb37fa3693c6f34287eec0dc62fe/designs/cache_options.md?plain=1#L126).
1.0.0
The sync period should use the default value (10 Hours) unless there are very good reasons against it.
The sync period is 5 Minutes.
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
The keycloak-realm-operator uses a sync period of five Minutes (see https://github.com/keycloak/keycloak-realm-operator/blob/main/cmd/manager/main.go#L108). This causes a massive load on the Kuberntes and Keycloak APIs, leading to throttling and an overall sloweness of the operator (when using many resources).
The default sync period is ten hours, and you should
(see https://github.com/kubernetes-sigs/controller-runtime/blob/685db561ba77cb37fa3693c6f34287eec0dc62fe/designs/cache_options.md?plain=1#L126).
Version
1.0.0
Expected behavior
The sync period should use the default value (10 Hours) unless there are very good reasons against it.
Actual behavior
The sync period is 5 Minutes.
How to Reproduce?
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: