botkube VS kube-state-metrics

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.

git clone https://github.com/kubernetes/kube-state-metrics.git

https://github.com/kubernetes/kube-state-metrics/blob/main/docs/pod-metrics.md According to this github repo completion is responsible of termination date if I correctly understood .

kube-state-metrics

Those are entirely different types of data. You can get that from something like kube-state-metrics

I've never had a cluster of that size, so take it with a grain of salt - but maybe you could try purpose-based sharding? KSM has allowlist and denylist config flags, for configuring which metrics it exposes https://github.com/kubernetes/kube-state-metrics/blob/main/docs/cli-arguments.md

Kubernetes itself will not notify you, the way I've seen people do this, is to use something like kube-state-metrics or node_exporter, export that to Prometheus (or preferrably VictoriaMetrics because Prometheus is terrible IMO), and then setup alarms on that with alertmanager or equivalent, or just look at dashboards regularly with Grafana. Realistically I recommend only setting alerts on disk usage and application/database latency. CPU and memory utilization isn't a great metric to alert on a lot of the time.

Another tip that you could consider spelling out a little more, is to monitor the number of resources created by Kind. This is somewhat mentioned for jobs and services, but any Kind of which thousands of resources are created will put stress on the control-plane. The total number of resources per namespace/cluster can be monitored with kube-state-metrics. KSM does not emit metrics of resources created from CRDs. These metrics can be implemented with KSM's custom resource state metrics: https://github.com/kubernetes/kube-state-metrics/blob/main/docs/customresourcestate-metrics.md

We then have various other Metrics called Kubernetes Workload Metrics. These are the dashboards with names that start with “Kubernetes / Compute Resources / Workload”. These dashboards are specific to the services you are running. They take into account the Kubernetes Workloads in your various namespaces, using kube-state-metrics. For a closer look, check out otel_demo_app_k8s_dashboard.tf.

The first step to optimizing costs is gaining visibility into your costs using tools. Kubernetes provides a Metrics Server and kube-state-metrics that can give you the overall picture of resource utilization by your cluster. There are more tools that provide more granular breakdowns and provide dashboards with business metrics, infra cost, and alerting functionalities. Here are some strategies to optimize your resource utilization and cloud bills on k8s.