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
Describe the bug Hi !
We have followed the instructions on how to install and configure botcube, but unfortunatly the bot is unresponsibe.
Looking at the logs, we can see a lot of not found messages
not found
Also, is it normal that the bot is away ?
To Reproduce Installed with Helm2
helm upgrade helm-botkube --namespace botkube \ --set config.communications.slack.enabled=true \ --set config.communications.slack.channel=k8s \ --set config.communications.slack.token=xoxb-xxxxxxxxxxxxxxxxxxxxxxx \ --set config.settings.clustername=abcd \ --set config.settings.allowkubectl=false \ --set image.repository=infracloudio/botkube \ infracloudio/botkube
Expected behavior
Screenshots
Additional context
The text was updated successfully, but these errors were encountered:
Tested with deploy-all-in-one.yaml and it working like a charm :) !
deploy-all-in-one.yaml
Sorry, something went wrong.
That's a bug in documentation side. We have updated the helm3 commands but helm2 still pointing to older syntax. Let me fix it
Successfully merging a pull request may close this issue.
Describe the bug
Hi !
We have followed the instructions on how to install and configure botcube, but unfortunatly the bot is unresponsibe.
Looking at the logs, we can see a lot of
not found
messagesAlso, is it normal that the bot is away ?
To Reproduce
Installed with Helm2
Expected behavior
Screenshots
Additional context
The text was updated successfully, but these errors were encountered: