The cloud, Kubernetes, CI/CD, DevOps, GitOps… the last five years have seen a huge transformation in how organizations are architecting and shipping applications. It’s hard to keep up with the pace and learn all of this new tech! Nearly 55% of respondents to Canonical’s 2021 Kubernetes and cloud native operations report highlighted how the lack of sufficient in-house skills and people power is the biggest challenge that Kubernetes brings to businesses.

Sysdig maintainers are thrilled to announce the latest release of our beloved OSS tool for analyzing and/or recording the activity of processes and containers on a Linux system. You can find the full CHANGELOG in the GitHub repository, but here are some highlighted features: Note: The 0.29.1 has been released with a bug fix shortly after we started to write this post.

Containers are one of the most popular ways for businesses to deploy applications. They provide an easy method of packaging applications into self-sufficient units that can be used, moved around, and re-used in any number of ways without breaking the overall functionality of your software. With the possible exception of serverless architecture, containerization is perhaps the best way to achieve smooth, seamless application deployment and minimal hassle with updates and application maintenance.

Prometheus is considered the de facto standard for Kubernetes application metrics, but running it yourself can strain engineering time and infrastructure resources when your usage grows. In March, we announced the general availability of Google Cloud Managed Service for Prometheus to help you offload that burden, and today, we’re excited to announce a new low-cost, high-usage pricing tier designed for customers who are moving large volumes of Kubernetes metrics over to the service.

For those who missed the live conversation, we had a great chat with Nana Janashia around taking the next click in with Kubernetes. As one of the great equalizers between the development and operations teams, Kubernetes has a duality of generics and opinions to power your workloads. This duality can be a complex one to navigate not only dealing with a new paradigm of idempotency and ephemerality but also dealing with a vast amount of choice and seemingly granular.

Many organizations are adopting Kubernetes to gain agility and increased time-to-value. However, complexity, security, and a shortage of IT skills are the top challenges that prevent organizations from effectively deploying Kubernetes. Complexity Kubernetes requires the selection and integration of a host of component services, which makes do-it-yourself (DIY) deployments beyond the scope of most organizations. Kubernetes management also differs significantly from traditional IT environments.

There are many different ways to run a Kubernetes cluster, from setting everything up manually to using a lightweight distribution like K3s. K3s is a Kubernetes distribution built for IoT and edge computing and is excellent for running on low-powered devices like Raspberry Pis. However, you aren’t limited to running it on low-powered hardware; it can be used for anything from a Homelab up to a Production cluster.

Welcome to the second post in a series of “Implementing Microservices on AWS with the Twelve-factor App”. In the first post, we covered the areas around the codebase, configuration, code packaging, code builds, and stateless processes. This article will go through the remaining areas for best practices in microservices. Let’s start the discussion with Port mapping!

Hey everyone. We’re excited to announce the release of Calico v3.23! Thanks to everyone in the community who contributed to the release. We could not have fitted this many improvements in without you. To view the detailed release notes, please visit us here. While we have many improvements in this release, here’s a brief overview of some of the larger features to be aware of.