Skip to content
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

Closed
vishal-biyani opened this issue Oct 18, 2019 · 18 comments
Closed

Are you using BotKube? We would love to hear! #202

vishal-biyani opened this issue Oct 18, 2019 · 18 comments

Comments

@vishal-biyani
Copy link
Contributor

vishal-biyani commented Oct 18, 2019

Hey Folks,

Please comment on this issue if you are using BotKube. We would love to hear about:

  1. How are you using BotKube?
  2. What else would you love to see in BotKube?
  3. If you are ok to share, please mention the name of the company/organization using BotKube. We will include it in the "Users of BotKube" list in README!
  4. Feel free to get in touch with us on BotKube Slack
@PrasadG193 PrasadG193 pinned this issue Oct 18, 2019
@timstoop
Copy link

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.

@Surbhidongaonkar Surbhidongaonkar unpinned this issue Dec 5, 2019
@testlabauto
Copy link

Hi,
I'm using the webhook after learning about botkube from a PR for kubewatch. I use the webhook to start tests automatically post deploy. The webhook is a huge improvement over the kubewatch one.
Thanks for making botkube!

@sanketsudake sanketsudake pinned this issue Dec 19, 2019
@vishal-biyani
Copy link
Contributor Author

@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.

@vishal-biyani
Copy link
Contributor Author

@testlabauto Thanks and glad to know. Please feel free to file any issues if you want certain features or see any bugs in BotKube

@timstoop
Copy link

@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.

Done: #231

@codenio
Copy link
Contributor

codenio commented Dec 20, 2019

I use the webhook to start tests automatically post deploy.

Thanks @testlabauto , the way you use botkube sounds great 👍.

@PrasadG193, could this added under usecase section in docs?

@vfiset
Copy link

vfiset commented Feb 21, 2020

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

@vfiset
Copy link

vfiset commented Feb 21, 2020

And I'm a complete moron. I guess the node ressource will do exactly what I want. Trying it first thing tomorrow :)

@PrasadG193
Copy link
Collaborator

Hey @vfiset,
You can configure BotKube to get notifications about error events in Node (please have a look at https://www.botkube.io/configuration/).
Additionally, from the upcoming release, If you want to get notification about a change in the specific field of resource spec/status, you can configure that too - you can set jsonpath to the field in updateSettings (e.g https://github.com/infracloudio/botkube/blob/develop/deploy-all-in-one.yaml#L152)

@Zer0-bit
Copy link

Zer0-bit commented Feb 25, 2020

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.
I see there's a pull request from @PrasadG193 but as of now this feature isn't yet there...

@vaibhavp vaibhavp unpinned this issue Mar 26, 2020
@vaibhavp vaibhavp pinned this issue Mar 26, 2020
@nnao45
Copy link
Contributor

nnao45 commented May 21, 2020

Hi team.

  1. When using "easy" operate k8s at slack with devops teams, and love to looks pod log.
  2. want to look events summary, or command history
  3. CyberAgent/AI Div.
  4. 👍

@niks3089
Copy link

niks3089 commented Jun 9, 2020

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 )

@rahulchheda rahulchheda unpinned this issue Jun 15, 2020
@gmkumar2005
Copy link
Contributor

gmkumar2005 commented Jun 17, 2020

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.

@vishal-biyani
Copy link
Contributor Author

Hi @gmkumar2005 Thanks for the info. Could you please elaborate on what enterprise feature would help you specifically?

@PrasadG193 PrasadG193 pinned this issue Jun 17, 2020
@gmkumar2005
Copy link
Contributor

  1. Restrict the bot to only one name namespace. Or current namespace.
  2. Kubectl commands should be allowed executed only for a designated user or groups.
  3. Web interface for the administrator to apply filters/restrictions dynamically.
  4. Warning messages indicating alerts will be received potentially by un-monitored channels.
  5. The connections should expire after a defined schedule. Should start working only when explicitly enabled.
  6. OTP on an alternative medium for destructive commands.
  7. Microsoft Teams support.
  8. Kubectl command line options are too rigid. The Bot could be smarter eg: Ignore the spell checks, Respond with nearest match of actual resource names.

@hr1sh1kesh hr1sh1kesh unpinned this issue Jul 9, 2020
@PrasadG193 PrasadG193 pinned this issue Sep 26, 2020
@akankshakumari393 akankshakumari393 unpinned this issue Sep 28, 2020
@PrasadG193 PrasadG193 pinned this issue Sep 30, 2020
@akankshakumari393 akankshakumari393 unpinned this issue Oct 1, 2020
@PrasadG193 PrasadG193 pinned this issue Oct 13, 2020
@hr1sh1kesh hr1sh1kesh unpinned this issue Dec 7, 2020
@PrasadG193 PrasadG193 pinned this issue Dec 29, 2020
@ghost
Copy link

ghost commented Feb 25, 2021

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:

slack:
    enabled: true
    channels: ["@joe.barbado", "@frankie.sucks", "devel-status"]

@maxisam
Copy link

maxisam commented Apr 6, 2021

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.

https://docs.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/connectors-using

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.

@sigmabaryon sigmabaryon unpinned this issue Apr 26, 2021
@PrasadG193 PrasadG193 pinned this issue Nov 26, 2021
@hdkshingala hdkshingala unpinned this issue Apr 20, 2022
@pkosiec
Copy link
Member

pkosiec commented Mar 31, 2023

Thank you for the feedback. Closing this issue in favor of #647. See you there! 👋

@pkosiec pkosiec closed this as completed Mar 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests