botkube VS HomeLab

I think a great tool that you can use for your projects is Botkube, it can be used to view your reports and provides updates in chat platforms including slack, discord and Microsoft teams.

💡 Tip To make the code-snippets more readable, I skipped the error handling. However, it will be useful if you will add error handling for the final implementation. You can check the full gh source-code for the reference.

Botkube v0.17.0 is here, and it's huge! We've introduced a plugin system for sources and executors along with the first plugin for Helm. Botkube is the most modern ChatOps tool for Kubernetes!

The new Botkube Slack app provides more great interactive features and better security when compared to the legacy Botkube Slack app. We announced the new socket mode Slack app in the Botkube v0.14.0 release notes. The new Slack app has some specific requirements and a new installation process, so let's have a look at how to get started with the most modern ChatOps tool for Kubernetes!. You can also use the Botkube installation documentation to get started, but this post is to give you more context about the changes to the new app and some caveats to watch out for.

The latest version of Botkube is here, v0.16.0. Like peanut butter and chocolate, we've brought together two great parts of Botkube to make your life working with Kubernetes even tastier easier. Botkube is the most modern ChatOps tool for Kubernetes!

We have fixed several bugs in BotKube that were reported to us by users. We also spent some time refactoring code and increasing test coverage to improve the quality of BotKube. You can see the list of bug fixes in the changelog.

We have an exciting early release of Botkube, just in time for KubeCon! We've been working as fast as we can to get some great new features ready to release. Here's v0.15.0 of Botkube, the most modern ChatOps tool for Kubernetes!

BotKube, welcome to Kubeshop! We're happy to have the most modern ChatOps tool for Kubernetes join the team.

Hi all, we just released Botkube 0.15 with which Slack users can now run kubectl commands without typing actual commands at the bot (just @botkube k) as well as grep-like filtering of the commands’ output. Here is a demo:

Hey, not yet - currently we do support Slack, Discord, Mattermost and Teams. Here's the issue you can watch for the updates around Telegram support: https://github.com/kubeshop/botkube/issues/50.

And if you are interested how I've done it: https://github.com/Michaelpalacce/HomeLab

Example of a service that is being backed up (see backup.velero.io/backup-volume): https://github.com/Michaelpalacce/HomeLab/blob/master/Helm/apps/uptimekuma/templates/deployment.yaml

But for me https://github.com/Michaelpalacce/HomeLab/tree/master/cluster/homelab/apps

So I've been trying to get botkube to work, but it seems to me like the helm chart documentation is outdated? I've been looking at the values and trying to make things work and it didn't really work for me.. https://github.com/Michaelpalacce/HomeLab/blob/master/cluster/homelab/apps/botkube/helmrelease.yaml is what I tried

And here is some documentation and specifics I've ran into. https://github.com/Michaelpalacce/HomeLab/blob/master/docs/Backups.md

Also for configuration storage and git, I recommend taking a gitops approach to things. You can checkup FluxCD2. Here is my repo for reference https://github.com/Michaelpalacce/HomeLab

A few suggestions and thinks I wish I knew when I started ( personal opinions incoming ): 1. Get a single well sized server ( I'd go for 8 cpus .. And like more than 16 gigs of ram and 250+ ssd, ideally m.2 nvme ). Don't bother with raspberry pis.. Check my profile for my previous post to see a comparison of raspberry pi cluster and a x86 cluster... 2. Install proxmox to do virtualization 3. The majority of People in this sub hate kubernetes and the minority is scared to speak, but install k3s on the vms you spin up, this way you can scale resources and not worry about some elaborate setup of which containers go to which node and how to setup tls offloading, load balancing and much much much more as kubernetes will handle it for you. ( bonus since you are a devops engineer so you are probably used to kube clusters ) 4. Use Velero to do restic backups to s3 for services that are critical like dbs and password managers etc. 5. Do everything with ansible or GitOps! My personal homelab is here: https://github.com/Michaelpalacce/HomeLab utilizing ansible, flux for GitOps and renovate to keep my services up to date ( note to say my cluster spin up isn't as nice as I want it to be since when provisioning I have a Dependency on some secrets which I do manually.. But this is only first cluster setup ) 6. Setup a VPN and administrative services on the raspberry pi you have lying around. Personally my VPN is on the router but if yours doesn't support it, do that. 7. After you are done setting everything up and you have a backup, format the drives and reinstall the vms and re set everything up. Document the process, write automation scripts until satisfied... I genuinely recommend you do this like 3 times...... 8. Vpn I guess a lot of people like wireguard or adguard home... Doesn't really matter as long as it's not open vpn and it supports multiple threads. 9. Setup nodered for some automation around your new home, you'll love it. 10. Firefly is amazing! 11. Make sure that your CSI ( Container storage interface ) supports replication. Keep 3 replicas of critical volumes! 11. If you need any help, don't forget to ask :) personally shoot me a dm and I'll do my best to help, but I'm sure most of us here would