Many enterprise customers are using ELK to store the logs from their Kubernetes clusters. Others are using solutions the cloud provider offers like Stackdriver or Cloudwatch. While ELK is difficult to configure and to operate, managed solutions are quite easy to use but they lead into a Vendor Lock-In. Both solution models are quite expensive if you want to store a big number of logs and if you have more than a few Kubernetes clusters. Weiterlesen…
Many people are leveraging fluentd, fluent-bit or the ELK-stack in combination with filebeat to collect their logs from Kubernetes clusters. These options are often complicated to configure or not flexible enough to use for different teams. We were looking for an easy way to collect our logs. Besides that, the customer wanted an option to do this, too. In the end we decided to use the logging-operator by banzaicloud. It is utilizing a DaemonSet of Weiterlesen…
While countless companies are starting to use Kubernetes to offer their services and applications, many are experiencing the classic problems of “Day-2 operations”: The systems are often not optimized, maintenance aspects are missing, or observability concepts are not sufficiently or incorrectly implemented. A common problem is that existing monitoring and logging solutions cannot be used, because they do not fit the requirements of distributed systems and Multi-Cluster-Environments. Problems of monitoring distributed systems But why is Weiterlesen…
Using Gardener Machine-Controller-Manager and Tailscale to extend a local Raspberry-Pi K3s cluster with cloud instances. tl;dr watch the Video from Christoph presenting this solution at the Gardener Meetup Intro Like a lot of Kubernetes enthusiasts, I grabbed a couple of Raspberry Pis, followed the instructions of Alex Ellis, and created a K3s cluster. I don’t want to repeat this instruction here, Alex did a great job explaining how to prepare the Machines and a K3s Weiterlesen…
