Operations | Monitoring | ITSM | DevOps | Cloud

Kubernetes 1.23 is about to be released, and it comes packed with novelties! Where do we begin? This release brings 45 enhancements, on par with the 56 in Kubernetes 1.22 and the 50 in Kubernetes 1.21. Of those 45 enhancements, 11 are graduating to Stable, a whopping 15 are existing features that keep improving, and 19 are completely new. The new features included in this version are generally small, but really welcomed. Like the kubectl events command, support for OpenAPI v3, or gRPC probes.

Epinio, the application development engine for Kubernetes, is meant to take you from app to URL in one step. It does that by either applying buildpacks to your app or using a pre-built docker image. Epinio installs into any Kubernetes cluster to bring your application from source code to deployment and allow for developers and operators to work better together.

As Kubernetes becomes the key target environment across many organizations, it automatically becomes an essential topic for developers. However, Kubernetes was created for operations and, unless you spend a considerable amount of time learning and specializing yourself, it is still challenging to use. Developers should rather focus on delivering applications instead, and a developer or application-focused platform is needed to enable that.

Since we launched Qovery in January 2020, we offered free hosting ("Community" plan) for every developer. Providing free hosting was the perfect way to get product feedback and iterate with our users without the cost constraint. As our hosting infrastructure costs have drastically grown within the last 18 months, we had to reinvent our free offer. In a nutshell, we will continue to offer free hosting to involved community members only. Keep reading to know more 👇

This is the most exciting feature we launched since Qovery v2 has been released - the Preview Environment feature!

Kubernetes management can be daunting for developers who don’t have specialized understanding of the orchestration technology. Learning Kubernetes takes practice and time, a precious commodity for devs who are under pressure to deliver new applications. This post provides direction on what you need to know and what you can skip to take advantage of Kubernetes. Let’s start with five things you need to know.

Today, Kubernetes 1.23 release candidate was made available upstream for testing and experimentation. General availability is planned for December 7th, so now is the time to report back any issues or bugs. Developers, DevOps and open source software enthusiasts can try out the latest features using MicroK8s. MicroK8s is a lightweight, CNCF-certified Kubernetes distribution with a streamlined UX.

Welcome to a new update of “What’s new in Sysdig.” Happy All Saints’/Souls’ Day! Happy International Pianist Day! Happy Thanksgiving! Happy Diwali! Glad alla helgons dag. The “What’s new in Sysdig” blog has been rotated to a new team, and this month, Peter Andersson is responsible for the publishing. Thanks to Chris Kranz for an excellent job compiling these articles earlier.

A single Kubernetes cluster expends a small percentage of its total available assigned resources on delivering in-cluster networking. We don’t have to be satisfied with this, though—achieving the lowest possible overhead can provide significant cost savings and performance improvements if you are running network-intensive workloads.

If GitHub stars are any indication, Prometheus has been doubling in usage year over year since its inception. While at Moogsoft we love Prometheus as the metrics foundation of our observability platform, there were some challenges to overcome to make it the rock-solid piece of our stack it is today.

Kubernetes is viewed as one of the great equalizers between development and operations teams. Simply write a manifest and the declarative power of Kubernetes is off to fulfill your desired state. Kubernetes is certainly pluggable and has the ability to be extended / opinions being swapped internally. As any IT organization can tell you, even with Kubernetes there is a lot of integration work, and several parts of the stack such as IaC have been left outside of Kubernetes.

Kubernetes dominates the container orchestration market in every way. According to the latest State of Kubernetes and Container Security study, 88% of enterprises utilise Kubernetes to manage a portion of their container workloads. Kubernetes and other orchestration systems have given software deployment and management a new level of robustness and customization. They also brought attention to the current security landscape's shortcomings.

Making an Open Source Software with sensitive data and dozens of external integrations is a real challenge, here are feedbacks and tradeoffs we've made.

Back in May, we announced the Kubernetes integration to help users easily monitor and alert on core Kubernetes cluster metrics using the Grafana Agent, our lightweight observability data collector optimized for sending metric, log, and trace data to Grafana Cloud. Since then, we’ve made some improvements to help our customers go even further.

In this article, we’ll cover the three main challenges you may face when maintaining your own Prometheus LTS solution. In the beginning, Prometheus claimed that it wasn’t a long-term metrics storage, the expected outcome was that somebody would eventually create that long-term storage (LTS) for Prometheus metrics. Currently, there are several open-source projects to provide long-term storage (Prometheus LTS). These community projects are ahead of the rest: Cortex, Thanos, and M3.

Fast build times are great, which is why we aim for less than 5m between merging a PR and getting it into production. Not only is waiting on builds a waste of developer time — and an annoying concentration breaker — the speed at which you can deploy new changes has an impact on your shipping velocity. Put simply, you can ship faster and with more confidence when deploying a follow-up fix is a simple, quick change.

It’s that time again; we’re really happy to announce Calico v3.21! As always, thank you to everyone who contributed to this release! For detailed release notes, please go here. Alongside the usual-but-essential bug fixes and other improvements, there are some big new improvements to be aware of.

Cloud-native transformations come with many security and troubleshooting challenges. Real-time intrusion detection and the prevention of continuously evolving threats is challenging for cloud-native applications in Kubernetes. Due to the ephemeral nature of pods, it is difficult to determine source or destination endpoints and limit their blast radius. Traditional perimeter-based firewalls are not ideal fit for Kubernetes and containers.

Leveraging Terraform, which is an infrastructure-as-code platform, is a great match. Using both technologies together is becoming more mature and there have been some great pieces around the art of the possible between the two platforms. Though if you are unfamiliar with both, this guide will get you up and started with both Terraform and Shipa together. In this example will be using Terraform to create all of the necessary Shipa resources to deploy to a Kubernetes cluster.

So you’ve just created a new project and want to start distributing it, but you still don’t know how to manage its deployment. Then there’s the monitoring, network request, and a lot of other problems related to modern apps. At the same time, you want to avoid working directly with AWS due to its intricacy.

I’m sure most of us have heard this saying before, and if you are in the DevOps space, I’m sure this is a scenario that you deal with daily. Most of us started even before we even had all these nice terms, such as DevOps, SREs, DevSecOps, and so many others, when we were all Sys Admins.

Securing a cloud-native environment, such as SUSE Rancher, requires unique considerations. New abstractions like containers, plus the dynamic nature of a Kubernetes orchestrated environment can hamper visibility, especially for legacy tools that aren’t designed for containers and cloud. To help, Sysdig and SUSE have launched a SUSE One Partner Solution Stack designed to not only showcase our joint solution, but also to provide easy ways for you to get started.

We are very excited to announce that you can now install Shipa from the SUSE Rancher Marketplace. Installing Shipa On-Prem can now be done with a click-to-install inside of SUSE Rancher. Follow this quick guide to get you up and started with Shipa if you are leveraging SUSE Rancher.

Intel and Canonical collaborate to build and publish OpenVINO™ container images based on the Ubuntu ecosystem. This work aims to provide trusted, secure, and developer-friendly container images for AI/ML applications in many industries.

The Kubernetes API is the front end of the Kubernetes control plane and is how users can interact with their clusters. In essence, it’s the interface used to manage, create, and configure the cluster and the state of objects. Using a standard API, Kubernetes allowed teams to focus on constructs and consume infrastructure across different providers.

This series shows you how to get started with infrastructure as code (IaC). The goal is to help developers build a strong understanding of IaC through tutorials and code examples. Infrastructure as Code (IaC) is an integral part of modern continuous integration pipelines. It is the process of managing and provisioning cloud and IT resources using machine readable definition files.

As a DevOps Engineer, one day you’re performing magic in the terminal, settling clusters, and feeling like a god. On some other days, you feel like a total fraud and scam. Errors and bugs appear from everywhere, you don’t know where to start, and you don’t know where to look. Sadly, days like this come far too often. To be more specific, what often causes these bad days is none other than Kubernetes itself.

In case you missed the big news, after almost two years in beta and early access phases, Civo is now general availability! Find out what this means for Civo and the future of the platform over at our blog. We've also launched the first-ever Civo Hackathon! This is an initiative to bring together developers, architects, experts, and students from across the globe to develop innovative Kubernetes projects on Civo.

Helm has some limits, discover how we extended functionnalities with Rust.

In our previous post , we focused on tips for making the transition and migration to Kubernetes a smoother, and less painful process. In this post, we’d like to now provide some tips from the operational trenches for future-proofing your Kubernetes operation, after making the move. Kubernetes, as a software-driven system, has many benefits for engineers and DevOps teams to take advantage of.

Kubernetes has evolved into the leading platform to build your microservices systems. Given its increased maturity over the past few years as well as the robust ecosystem which has been built around its technology, Kubernetes has become more production-ready than ever. Nevertheless, it still has its own unique set of challenges. In particular, it brings a lot of complexity into play with its adoption.

With the Calico 3.10 release, Dynamic Packet Capture is available in Dynamic Service Graph. This means users who require self-service, live troubleshooting for microservices and Kubernetes workloads can capture and evaluate traffic packets on endpoints without writing a single line of code or using any 3rd-party troubleshooting tools. Users don’t need to learn about or have knowledge of kubectl or YAML to troubleshoot their microservices and Kubernetes cluster.

The Telegraf 1.20.3 release changed the official Telegraf DockerHub image to no longer run the Telegraf service as root. With this change, the Telegraf service runs with the least amount of privileges in the container to enhance security given the wide extensibility and array of plugins available in Telegraf.

Monitoring cloud-native systems is hard. You’ve got highly distributed apps spanning tens and hundreds of nodes, services and instances. You’ve got additional layers and dimensions—not just bare metal and OS, but also node, pod, namespace, deployment version, Kubernetes’ control plane and more. To make things more interesting, any typical system these days uses many third-party frameworks, whether open source or cloud services.

In this blog post, I will be talking about label standard and best practices for Kubernetes security. This is a common area where I see organizations struggle to define the set of labels required to meet their security requirements. My advice is to always start with a hierarchical security design that is capable of achieving your enterprise security and compliance requirements, then define your label standard in alignment with your design.

Kubernetes is everywhere! In the public and private cloud, and from the enterprise to startups, the majority of IT executives around the world have explored Kubernetes, and how it has evolved the way many organisations are developing and deploying their applications. But what is scary about it, and how can organisations better leverage one of the greatest tools in the field while overcoming the biggest challenges facing CIOs when adopting Kubernetes?

KubeCon/CloudNativeCon North America 2021 was a whirlwind of sessions, talks, panels, bonding, and learning. As it was a hybrid event, Civo was represented both in person at a booth that featured Sophia and David from our North American team, as well as virtually through our online booth and talks. Plus, we made an announcement of the General Availability of Civo Kubernetes at the event!