-
Notifications
You must be signed in to change notification settings - Fork 289
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
Are you using BotKube? We would love to hear! #202
Comments
Hi, So, I've been looking into this for a while now and although we have it deployed, we hardly do anything with it. We're just kinda keeping track of what will be possible at some point. What we think would be a really great addition that would make the bot very useful is something like scripted automated debugging. For instance, if a Pod fails due to OOMErrors, it would be very helpful if the bot would tell so. Also, if it's a failing liveness check or when a Pod errors and maybe show the last 10 or so lines of log from that container as well. Those kind of automated responses I think would be very welcome. We are considering doing the work on that ourselves, but we're just a small company and there are more important things for the time being. But these kind of assistance by the bot would be very useful, way more useful than just showing modified resources. |
Hi, |
@timstoop Thanks for your feedback - this is really helpful. Do you mind creating an issue and file whatever features you would like to see - and we can try to have them developed in upcoming releases. |
@testlabauto Thanks and glad to know. Please feel free to file any issues if you want certain features or see any bugs in BotKube |
Thanks @testlabauto , the way you use botkube sounds great 👍. @PrasadG193, could this added under usecase section in docs? |
Hi! I am not using it, yet! I came here out of reading the issues on kubewatch as well ;) one thing I am not able to tell from reading the docs is: is there a way to get the system events like node*pressure, evictions and so on? Something I don't seem to get from kubewatch. Thanks for your work. I will try it anyways in the next few days. It seems much better than you know who! Cheers |
And I'm a complete moron. I guess the node ressource will do exactly what I want. Trying it first thing tomorrow :) |
Hey @vfiset, |
We would use it if it had MS Teams support, as of now i don't really want to start using Slack separately just for this. |
Hi team.
|
Hi team, I work at Nimbella and recently we launched Commander, a cross-platform serverless framework to develop custom bots/commands for Slack, Mattermost & Teams where you write code and run it anywhere including the messaging platforms. I think this could be useful for BotKube because you can write your integrations for Teams without having to worry about the complexity of writing a Teams Bot, using Microsoft Bot Framework or deploying it on Azure. Commander takes care of all of it and you will be writing only your app logic! We have open-sourced such minibots as command-sets in our github repo and we will be releasing Teams support soon (in 2 weeks). In case you're interested, I can help in writing an integration for Teams. Let me know! (Note: It's super-fast to write and run custom commands. Normally it would take just a day or two ) |
I have just deployed botkube on OpenShift it works well as documented. This will be very useful during UAT and Golive preparations. Like to see some more enterprise features. |
Hi @gmkumar2005 Thanks for the info. Could you please elaborate on what enterprise feature would help you specifically? |
|
Well, I would like to see a simple feature: We use BotKube in our Slack to notify about Deployment tool status directly to responsible person "@name.surname" instead of channel. It would be great, if BotKube could mention status to more persons and also public channel. For example like this:
|
Is it possible to use MS Team without public endpoint? like using it as a webhook. I tested webhook but it doesn't work with MS Team's webhook connector. I think the webhook in MS Team has a specific format. Here is how kubewatch does it vmware-archive/kubewatch@4cc8a76 I feel like this should be a very popular feature because not every cluster has outside access. |
Thank you for the feedback. Closing this issue in favor of #647. See you there! 👋 |
Hey Folks,
Please comment on this issue if you are using BotKube. We would love to hear about:
The text was updated successfully, but these errors were encountered: