Operations | Monitoring | ITSM | DevOps | Cloud

Hi, fellow Qovery readers, Albane here! 👋 To give you a bit of background, I joined Qovery in August 2021, initially as a Product Owner, then moved to a Product Marketing Manager position in March 2022. So yes, I’m all about our product. However, I also spend much time learning about our partner’s products, and that’s why, on April 27, 2022, I spent the day at the ExCel Centre in London to attend the annual AWS Summit.

In the Kubernetes (K8s) community, there is a huge misconception about CPU allocation and utilization. Even highly experienced SREs find themselves struggling with the way Kubernetes allocates CPU resources, leading to misconfigured CPU allocations and extremely negative outcomes. For starters, this results in significant quality degradation on important service components, introduced by behind-the-scenes CPU limiting (or throttling).

Things would be much simpler if we based all we built on Kubernetes on a single tenant type of architecture, meaning a single application running on the entire Kubernetes cluster with a single team who could access it. As teams scale Kubernetes adoption within their organizations, they see a different scenario instead, one with multi-tenant deployments performed by multiple teams and, most probably, across multiple clusters.

When I left Red Hat to join SUSE as a Technical Marketing Manager at the end of 2021, I heard about Harvester, a new Hyperconverged Infrastructure (HCI) solution with Kubernetes under the hood. When I started looking at it, I immediately saw use cases where Harvester could really help IT operators and DevOps engineers. There are solutions that offer similar capabilities but there’s nothing else on the market like Harvester.

We are in May 2022, and hundreds of startups have built their infrastructure on AWS using Qovery. This article will share the 10 best (and fancy) AWS architectures our customers have made. From the most classic architecture to the craziest 🤪 It can give you some ideas. Let's go 🚀

The release of Rancher Desktop 1.3.0 brings in some notable changes that are most visible on Mac and Linux while continuing to expand on experimental features.

Developed and released by Google in 2018 with contributions from IBM, VMWare, Red Hat, and other companies, the Knative project is designed to make it as simple as possible to build, deploy, and scale serverless containers across your existing Kubernetes infrastructure. By operating on top of Google Anthos, Knative for Anthos takes this even further by allowing developers to build and deploy applications across any hybrid environments that include both on-prem and cloud-hosted serverless clusters.