Operations | Monitoring | ITSM | DevOps | Cloud

Persistent storage is essential for any account-driven website. However, in Kubernetes, most resources are ephemeral and unsuitable for keeping data long-term. Regular storage is tied to the container and has a finite life span. Persistent storage has to be separately provisioned and managed. Making permanent storage work with temporary resources brings challenges that you need to solve if you want to get the most out of your Kubernetes deployments.

We’ve just released Calico v3.25! This milestone release includes a number of eBPF dataplane improvements designed to deliver an even faster upgrade experience, smaller memory footprint, and shorter eBPF networking object load time speed. But before we get into the details of these changes, let’s welcome and thank our new community problem-solvers who got their first contribution requests merged into our beloved project.

Looking back on the last 18 months, it is abundantly clear that one piece of technology found its moment more than any other: cloud. Essential to modern computing, cloud provides the capacity for businesses to run workloads with the flexibility and scale many firms would struggle to achieve with on-premise infrastructure. According to Flexera’s 2021 State of the Cloud Report, 90% of firms slightly or significantly increased their cloud usage due to the pandemic.

As we enter a new year, our team has made predictions for the coming year in the Cloud Native ecosystem.

As mentioned in our documentation, Cribl Stream is built on a shared-nothing architecture. Each Worker Node and its processes operate separately and independently. This means that the state is not shared across processes or nodes.This means that if we have a large data set we need to access across all worker processes, we have to get creative. There are two main ways of doing this: In this blog, we’ll walk through how to deploy a Stream leader, Stream worker, and Redis containers via Docker.