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?
to your account
Describe the bug
I've delete a statefulset via helm and slack notification sent by botkube. But I watch the channel and it keeps sending notifications.
Botkube puts the time to the footer of notification as follows:
BotKube | Today at 1:25 PM
But even latest notifications at 2:14 PM contain same footer "BotKube | Today at 1:25 PM".
When I type kubectl get events there is not any event which recently happened to send
notification to slack.
kubectl get events
Steps to reproduce the behavior:
I am not sure how to reproduce this behavior.
It should only send one time notification.
The text was updated successfully, but these errors were encountered:
@mstrYoda What version of BotKube you are using? You can get version with @BotKube version command.
Sorry, something went wrong.
Output of the command is "BotKube version: v0.8.0"
@mstrYoda I think this is already fixed in the develop branch. Could you please try deploying BotKube with latest image. You can use the following commands to use latest helm chart
$ helm repo add infracloudio https://infracloudio.github.io/charts
$ helm repo update
$ helm install --version v9.99.9-dev --name botkube --namespace botkube \
--set config.communications.slack.enabled=true \
--set config.communications.slack.channel=<SLACK_CHANNEL_NAME> \
--set config.communications.slack.token=<SLACK_API_TOKEN_FOR_THE_BOT> \
--set config.settings.clustername=<CLUSTER_NAME> \
--set config.settings.allowkubectl=<ALLOW_KUBECTL> \
--set image.repository=infracloud/botkube \
--set image.tag=latest \
@mstrYoda Please let us know if you see the problem in develop branch also
I've deployed botkube into our dev environment with specified configuration above. I will update my observation here when I deploy to production.
I've tested it and observed that no longer get duplicate events.
No branches or pull requests