The latest News and Information on DevOps, CI/CD, Automation and related technologies.
Running infrastructure at scale almost always guarantees dizzying complexity and anxiety-inducing pressure to maintain systems in a production environment. This is further exacerbated when multiple delivery teams require slight variations of the same infrastructure components, across several cloud providers, each with a different set of observability requirements. Gradually, production environments become large, unmanageable, difficult to change, and perhaps resembling the figure below.
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).
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.
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.
