Let's face it! Kubernetes is the standard for container orchestration, reshaping how we deploy and manage applications for the last 8 years - do you even remember when you run "docker run " on an application server? 😁. However, it's crucial to recognize that Kubernetes was never initially designed with the everyday developer in mind.

Time and time again we hear the same statements from FinOps teams with respect to what is holding back optimization of wasteful resource consumption. Engineers and App Owners are interested in helping but stop short at actually taking actions to reduce that waste. There are many reasons for this main sticking point when it comes to application owners and developers taking action.

It is essential to configure log rotation for Docker containers. Log rotation is not performed by default, and if it’s not configured, logs on the Docker host can build up and eat up disk space. This guide will teach us how to set up Docker log rotation. Logs are an essential piece of telemetry data. Logs can be used to debug performance issues in applications.

Time and time again we hear the same statements from FinOps teams with respect to what is holding back optimization of wasteful cloud resource consumption. Engineers and App Owners are interested in helping but stop short at actually taking actions to reduce that waste. There are many reasons for this main sticking point when it comes to application owners and developers taking action.

Kubernetes has revolutionized the world of container orchestration, enabling organizations to deploy and manage applications at scale with unprecedented ease and flexibility. Yet, with great power comes great responsibility, and one of the key responsibilities in the Kubernetes ecosystem is resource management. Ensuring that your applications receive the right amount of CPU and memory resources is a fundamental task that impacts the stability and performance of your entire cluster.

Last month, we announced our new GitOps Environment dashboard that finally allows you to promote Argo CD applications easily between different environments.

Picture this: It’s 2 p.m. and you’re sipping on coffee, happily chugging away at your daily routine work. The security team shoots you a message saying the latest pentest or security scan found an issue that needs quick remediation. On the surface, that’s not a problem and can be considered somewhat routine, given the pace of new CVEs coming out. But what if you look at your tooling and find it lacking when you start remediating the issue?