You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The botkube/kubernetes plugin encounters repeated memory access errors, specifically segmentation faults and nil pointer dereference issues, when configured with certain sources such as k8s-hpa-events. The issue consistently arises when attempting to monitor the autoscaling/v2 API group for horizontalpodautoscalers events related to HPA scaling. This results in the plugin crashing, and although the Plugin Health Monitor attempts to restart it several times, the plugin ultimately becomes deactivated.
I’m using BotKube v1.13.0, and the issue seems to occur during the plugin’s interaction with the Kubernetes API for these particular resources.
Expected behavior
With the k8s-hpa-events source enabled, BotKube should monitor horizontalpodautoscalers resources and successfully capture SuccessfulRescale events without crashing. These events should then be forwarded as notifications to Slack.
Actual behavior
When the k8s-hpa-events source is enabled, the following issues occur:
1. The kubernetes plugin crashes with a plugin process exited error.
2. The Plugin Health Monitor retries the plugin multiple times, but after several failures, it deactivates the plugin.
3. Repeated segmentation faults and memory access errors such as invalid memory address or nil pointer dereference are logged.
Steps to reproduce
1. Install BotKube v1.13.0 via Helm and configure it to monitor autoscaling/v2 API group and horizontalpodautoscalers resources.
3. Apply the following configuration for k8s-hpa-events:
Description
The botkube/kubernetes plugin encounters repeated memory access errors, specifically segmentation faults and nil pointer dereference issues, when configured with certain sources such as k8s-hpa-events. The issue consistently arises when attempting to monitor the autoscaling/v2 API group for horizontalpodautoscalers events related to HPA scaling. This results in the plugin crashing, and although the Plugin Health Monitor attempts to restart it several times, the plugin ultimately becomes deactivated.
I’m using BotKube v1.13.0, and the issue seems to occur during the plugin’s interaction with the Kubernetes API for these particular resources.
Expected behavior
With the k8s-hpa-events source enabled, BotKube should monitor horizontalpodautoscalers resources and successfully capture SuccessfulRescale events without crashing. These events should then be forwarded as notifications to Slack.
Actual behavior
When the k8s-hpa-events source is enabled, the following issues occur:
Steps to reproduce
Relevant logs:
BotKube version: v1.13.0
The text was updated successfully, but these errors were encountered: