-
Notifications
You must be signed in to change notification settings - Fork 295
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.
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
Increased resources consumption configuring some sources #1403
Comments
@mszostok posted this answer in Slack thread https://botkube.slack.com/archives/C01CR1KS55K/p1709121554586339
|
Hi @bygui86, good news! The issue has been resolved in #1425 which is now merged to the The Botkube 1.10 release is planned for next week but, in the meantime, could you please test Botkube from the latest The following command should do the trick: botkube install --repo https://storage.googleapis.com/botkube-latest-main-charts --version 0.0.0-2cb5eacc # add your own overrides here In case you use other way for the Helm chart installation, here are the details:
However, remember to keep the following overrides: image:
pullPolicy: IfNotPresent
registry: ghcr.io
repository: kubeshop/botkube
tag: 0.0.0-2cb5eacc # use the latest Botkube Agent image
plugins:
repositories:
botkube:
url: https://storage.googleapis.com/botkube-plugins-latest/plugins-index.yaml # use the latest plugins Hope that will fix your issue and you'll be able to upgrade to the latest Botkube. Cheers! |
@pkosiec thanks a lot for your effort! The memory consumption in the MR looks really promising! |
Before you submit the issue
helping-hands
.Description
We use Botkube mainly to receive alerts based on specific events.
Migrating from 0.18.0 to 1.8.0, we translated the configuration from old (0.18) to new (1.8) syntax, but we face some issues:
Please note that the above mentioned issues happen also with the default global_config coming out of the helm-chart with following sources enabled: k8s-all-events, k8s-create-events, k8s-err-events, k8s-err-with-logs-events, k8s-recommendation-events
Expected behavior
Even with many configured sources, Botkube should consume up to 1000m cpu and 1Gi mem, like in older versions <= 1.0.0
Actual behavior
With many configured sources, Botkube consumes up to 3000m cpu and 3Gi mem.
Steps to reproduce
Just deploy Botkube using following configuration:
expand
global_config.yaml
Slack threads
Versions
Kubernetes:
v1.28.4-gke.1083000
Platform:
GKE
Botkube:
1.8.0
The text was updated successfully, but these errors were encountered: