Half of the year is now over and even though we have plenty of news in stock for the next one, it’s now time to go through our quarter retrospective, so in case you missed anything, here are the most important releases of Q2!

When Kubernetes components like nodes, pods, or containers change state—for example, if a pod transitions from pending to running—they automatically generate objects called events to document the change. Events provide key information about the health and status of your clusters—for example, they inform you if container creations are failing, or if pods are being rescheduled again and again. Monitoring these events can help you troubleshoot issues affecting your infrastructure.

Expenditure on cloud computing services reached a mammoth 225 billion dollars in 2022. Companies start their cloud-native journeys with the best intentions and consume the many benefits including: But current cloud expenditure growth levels are unsustainable for many organizations and with 82% of organizations investing in FinOps staff it shows that cloud expenditure is top of mind in the c-suite.

At Qovery, we manage hundreds of Kubernetes clusters for our customers on different Cloud Providers. For most non-operational people, it’s hard to understand what it means behind the scene, the amount of work it represents, pitfalls we can encounter, and associated complexity. Our customers are coming for several reasons, but they’re all happy to have Qovery management on the Kubernetes maintenance and upgrade stack. On our side, it’s too many clusters to manage them manually.

In my previous blog post, I discussed how transitioning from legacy monolithic applications to microservices based applications running on Kubernetes brings a range of benefits, but that it also increases the application’s attack surface. I zoomed in on creating security policies to harden the distributed microservice application, but another key challenge this transition brings is observing and monitoring the workload communication and known and unknown security gaps.

A containerized approach to software deployment means you can deploy at scale without having to worry about the configuration of each unit. In Kubernetes, clusters do the heavy lifting for you—they’re the pooled resources that run the pods that hold your individual containers. You can divide each cluster by namespace, which allows you to assign nodes (ie the machine resources in a cluster) to different roles or different teams. Resource quotas limit what each namespace can use.

Building your own PaaS (Platform as a Service) can revolutionize the way you deploy and manage applications. One of the key advantages of a custom PaaS solution is its ability to streamline the complete application life cycle. With a well-designed PaaS environment, developers can easily package their applications, define dependencies, and deploy them seamlessly across various cloud environments. This simplifies the deployment process, reduces time-to-market, and ensures consistent application delivery.

June 27, 2023 We were excited to learn last week that GigaOm named Densify as both a Leader and an “Outperformer” in its new report “Radar for Cloud Resource Optimization”. This was particularly meaningful to us for a few reasons.

Health checks for cloud infrastructure refer to the mechanisms and processes used to monitor the health and availability of the components within a cloud-based system. These checks are essential for ensuring that the infrastructure is functioning correctly and that any issues or failures are detected and addressed promptly. Health checks typically involve monitoring various parameters such as system resources, network connectivity, and application-specific metrics.

Want to monitor all of your application's services? Our Standalone Agent allows you to monitor processes our standard integrations don't monitor by default, helping you effortlessly expand your monitoring capabilities. To help simplify the process of configuring our standalone agent, we're excited to announce the launch of our Standalone Agent's Docker image, available on Docker Hub under the name appsignal/agent.