Operations | Monitoring | ITSM | DevOps | Cloud

If you use Kubernetes in production, you should already know that monitoring and logging solutions are essentials if you want to make sure that your cluster is healthy at all times. Lack of computing resources and capacity misconfigurations are one of the most common causes of failed deployments. Especially if you are an operator, you always need to know the load of your cluster in order to perform capacity planning and setup autoscaling.

There are many articles and videos about practicing Continuous Delivery (CD) with applications, but not nearly as many for infrastructure. The same can be said for GitOps applied to infrastructure. That is a bit strange given that applications and infrastructure are almost the same today. Both are defined as code, and everyone stores code in Git repositories. Hence, GitOps is just as good of a fit for infrastructure as for anything else.

Helm charts are great. They combine high quality, ready-made runtime configurations for a huge number of applications with an incredible getting-started experience. There is literally no faster way to install a production-ready Grafana or Loki on Kubernetes than using helm install. Unfortunately, Helm charts can also be incredibly inflexible.

This community meetup took a deeper look into how the Civo marketplace can improve your Kubernetes workflows. Featuring some cool apps to try out, and how you can easily get involved with contributing, growing, and ultimately improving the marketplace. As well as talks from Civo's very own Saiyam Pathak and Kai Hoffman, we were also joined by community members Steve Miller and Jürgen Etzlstorfer.

In this guide, we are going to see what a Docker health check is and how to configure it for your Docker containers. A Health Check means to check the health of any resource to determine whether that resource is operating normally. Here, it is about checking the health of Docker containers. If you’ve been using docker containers in production, you might have noticed that docker checks the status of a container by using the status of the process (PID) launched from the Docker file command.

Companies are leveraging the power of Kubernetes to accelerate the delivery of resilient and scalable applications to meet the pace of business. These applications are highly dynamic, making it operationally challenging to securely connect to databases or other resources protected behind firewalls.

The SolarWinds® Papertrail™ team is excited to announce SolarWinds rKubeLog, an open-source project designed to streamline Kubernetes logging. rKubeLog allows you to forward logs to Papertrail from within a Kubernetes cluster without using a daemon or setting up application-level logging or a logging sidecar. rKubeLog is a quick and easy way to implement logging for applications running in Kubernetes clusters.

We continue with our series of articles on containers. First, we started with creating our own images with Docker Build and saw how to run them with Docker run. But today we will learn what Docker Compose is and start our journey into the world of container orchestration. Up to now we have managed containers manually and separately, which for some specific test may be valid and functional. But when the number of containers to manage starts growing, this method becomes infeasible.