Continuous delivery (CD) is an application development practice that involves automatically preparing code changes for release to a production environment. Combined with continuous integration (CI), continuous delivery is a key aspect of modern software development. Together, these two practices are known as CI/CD. Properly implemented CI enables developers to deploy any code change to testing and production environments late in the software development lifecycle (SDLC).

We’re excited to announce that with the release of Grafana Beyla 1.2, Kubernetes support is now fully integrated. With this update, the Grafana Beyla configuration now “understands” Kubernetes semantics to provide a more fine-grained selection of services to instrument. Beyla users can decorate metrics and traces with the metadata of Kubernetes entities, such as pods and deployments, that run the automatically instrumented services.

Azure Kubernetes Service (AKS) enables you to easily deploy and manage containerized applications in Azure while leveraging Microsoft resources such as development tools, security features, and more. As with any Kubernetes service, the sheer volume of containers being orchestrated makes monitoring AKS cluster health challenging, which can slow response times to critical incidents and create bottlenecks around long-term optimizations.

We're thrilled to announce the launch of our latest feature: Deployments! This game-changing addition is set to redefine how our users deploy and manage their applications, ensuring zero downtime and enhancing productivity.

Containers and microservices are revolutionizing how distributed applications are built, run, and optimized. They enable apps to be highly scalable. You can also isolate some areas for updates and patches without shutting down the entire application or service. Yet, managing containers and microservices at scale can be tricky. That’s where a container management platform like Kubernetes comes in – or, as you’ll see below, where the top Kubernetes alternatives shine.

Kubernetes and OpenShift are two major players in the container management space, each offering unique advantages and challenges. This article will discuss both these platforms, comparing their strengths and weaknesses. We will also explore their ideal use cases, and how a platform like Qovery bridges the gap between them. Whether you're a proficient DevOps or a developer, understanding these platforms can help you make the right choice for your container-based applications.

When we discuss observability for applications running in Kubernetes, most people immediately default to Metrics, Logs, and Traces – commonly referred to as the “three pillars.” These pillars are just different types of telemetry – signals that can be fed into observability platforms to help understand how an application behaves. But did you know that Kubernetes offers another valuable signal? When combined with the other signals, you get MELT.