If you are trying to learn your way around Continuous Integration/Delivery/Deployment, you might notice that there are mostly two categories of resources: We believe that there is a gap between those two extremes. We are missing a proper guide that sits between those two categories by talking about best practices, but not in an abstract way.

Speedscale is one of the finalists of the 2021 Atlanta Business Chronicle’s Fire Award! This award is Atlanta Inno’s premier recognition program, honoring the companies and organizations setting the local Atlanta innovation economy ablaze. Fire Awards, presented by Atlanta Inno in partnership with the Atlanta Business Chronicle, is a celebration of the early-stage businesses, enterprises and innovators who are doing special work to set Atlanta ablaze.

Let’s see how the Qovery billing is working as we are about launching the v2 in less than two weeks. Since we launched Qovery in January 2020, our product was free of charge for our “community” and “business” plans - even if on the pricing page it was mentioned the opposite. Making Qovery free was the perfect way to get product feedback and iterate with our users without the cost constraint.

Last year, VMware Tanzu Mission Control introduced data protection capabilities to help enterprises safely and confidently run critical workloads on Kubernetes. With this unique feature, enterprises can centrally manage data protection on their clusters across multiple environments, easily backing up and restoring their Kubernetes clusters and namespaces.

Elastic Cloud on Kubernetes (ECK) is an easy way to get the Elastic Stack up and running on top of Kubernetes. That’s because ECK automates the deployment, provisioning, management, and setup of Elasticsearch, Kibana, Beats, and more. As logging and metric data — or time series data — has a predictable lifespan, you can use hot, warm, and cold architecture to easily manage your data over time as it ages and becomes less relevant.

Introduction Since its introduction in 2014, Kubernetes has become the de-facto standard for deploying and scaling containers for cloud deployments and on-premises environments. Initially, it required a DevOps/SRE team to build, deploy, and maintain the Kubernetes deployment in the cloud. Now, all major cloud vendors provide a managed Kubernetes offering, freeing up teams to focus on managing and scaling the application instead of the infrastructure.

Calico is the industry standard for Kubernetes networking and security. It offers a proven platform for your workloads across a huge range of environments, including cloud, hybrid, and on-premises. Given this incredibly wide support, why did we decide to create a course specifically about AWS?

Since it first appeared in June 2014, Kubernetes has become something of a household name, at least in houses developers live in. The open source container orchestration platform makes challenges like load balancing, secret management, and portability a cinch and makes it easy to orchestrate large, highly scalable and distributed systems.

Kubernetes resource limits are always a tricky setting to tweak, since you have to find the sweet spot between having the limits too tight or too loose. In this article, which is a continuation of the Kubernetes capacity planning series, you’ll learn how to set the right Kubernetes resource limits: from detecting the containers without any limit, to finding the right Kubernetes resource limits you should set in your cluster.

In a recent post by ZDI, researchers found an out-of-bounds access flaw (CVE-2021-31440) in the Linux kernel’s (5.11.15) implementation of the eBPF code verifier: an incorrect register bounds calculation occurs while checking unsigned 32-bit instructions in an eBPF program. The flaw can be leveraged to escalate privileges and execute arbitrary code in the context of the kernel.