Operations | Monitoring | ITSM | DevOps | Cloud

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).

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.

Rancher Desktop is an all-in-one solution for container management on your desktop workstation. It provides an easily maintained Kubernetes installation that runs on your local machine and streamlines setting up containerized workflows in development. Assembling a Kubernetes cluster from scratch can be daunting, because multiple components must work in unison. With Rancher Desktop, you get everything preconfigured with one software download.

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.

Coming up in StackStorm 3.7.0 is a new feature that allows administrators of a StackStorm installation to “override” the default resource status that was specified by the pack owners. One of the benefits of StackStorm is the large variety of packs available on the StackStorm Exchange. But sometimes, users may not want the default content status provided by the community packs. We’re introducing a new feature into StackStorm 3.7.0 to make this easier to manage.

In this tutorial, you will learn how to work with the gRPC Golang library for microservice communication by creating a simple note-taking application. APIs and service-to-service communication are what make modern microservice architecture possible. REST is generally the preferred implementation pattern, but if you only use REST, you could miss out on the significant performance gains that gRPC can offer. gRPC can provide better speed and efficiency than REST APIs.