Helm is a package manager that makes it easy to deploy and manage Kubernetes applications. Our new Helm integration allows you to monitor the availability and status of the Helm-managed applications deployed in your Kubernetes clusters. In this post, we’ll show you how you can visualize the status of your Helm releases and use monitors to notify you of important changes in your Helm environment.

We have been busy at work in May creating new features and squashing bugs to delight those who use or have not yet started using Kubernetes. Finally, you can start finding Shipa back at in-person events, we just returned from Southern California at JFrog swampUP. We had many great conversations about what we have been working on, especially announcing the general availability of Shipa Insights, today!

The recent market turmoil has everyone from developers to CTOs and founders asking themselves a fundamental question “Is our cloud-deployment strategy recession proofs, and if not, how can we adapt to the new market realities?” Within enterprises of all sizes, leaders are asking hard questions, looking for ways to cut costs without negatively impacting growth.

Today’s developers use tools such as VMware Tanzu Application Platform and the Spring framework to build modern applications. However, to build best-of-breed, intelligent, data-centric applications, developers must utilize a unified, in-memory data layer. This enables development teams to truly scale their applications with the pace of business, especially when that business extends across the globe.

Kubernetes is currently the de-facto container orchestration system on the market. Both small and large companies adopt it, and all major cloud providers offer it as a service. However, Kubernetes is a complex and layered platform, so you can’t just jump into it. There are three essential stages for each application: design, deployment, and operation. This blog post will focus on operation, where you need to monitor and troubleshoot your deployed applications.

Kubernetes is today’s leading container management platform, due to its comprehensive API and developer-friendly features. Using Kubernetes, you can create scalable and reliable applications that run on-premises systems and public clouds. Its out-of-the-box features allow it to distribute hundreds of instances over data centers and keep them up and running. In order to catch up with the automation level of Kubernetes, developing and deploying applications requires more autonomy.

Calico v3.23 is out, and with it a lot of new features! This release marks a long-awaited milestone for me and my team, as it includes the Calico VPP data plane (beta). So now seems to be a good time to reflect on what this integration actually is, and why we built it.

Having trouble deploying Kubernetes in a highly available mode and have a backing remote database? This blog is for you. I will explain how to deploy K3s in HA configuration with an external database Postgres. K3s is a certified Kubernetes distribution for IoT and Edge computing. I deployed it on virtual machines in an IBM Z mainframe. Instead of etcd, I choose Postgres as my storage for my K3s clusters. I deployed Postgres in non HA mode.

After two years of virtual editions, KubeCon + CloudNativeCon Europe returned as a hybrid event, with its in-person portion held in Valencia, Spain, from May 16-20. As platinum sponsors of this year’s conference, Datadog held a booth where we showcased the latest updates to our Kubernetes monitoring solution, including the new Kubernetes resources overview, improved OpenTelemetry support, and the latest version of the Datadog Operator for Kubernetes.

Welcome to another edition of What’s New in Sysdig in 2022! The “What’s new in Sysdig” blog is now under my control! Hello, I’m Wes MacKay, a Sales Engineer based out of Dallas, TX working with the Sysdig US West Corporate team. I’m way too passionate about containerization, personal cloud storage, and automating my home life. In my spare time, I’m always looking for better Thai and Sushi restaurants in my area.

One of the best things about Kubernetes is just how absurdly flexible it is. You, as an admin, can shape what gets deployed into what is the best for your business. Whether this is a basic webapp with just a deployment, service and ingress; or if you need all sorts of features with sidecars and network policies wrapping the serverless service-mesh platform of the day. The power is there.

On May 11th, at Intel Vision, Densify won Intel Partner of the year for Software Innovation. This award recognizes the impact of our jointly developed offering: Intel Cloud Optimizer (ICO). <="" a=""> Working with Intel we launched a program for enterprise customers that combines Densify analytics software and Intel expert guidance to help match customer workloads with the cloud instances that enable the best performance at the lowest possible cost.

Calico Open Source is an industry standard for container security and networking that offers high-performance cloud-native scalability and supports Kubernetes workloads, non-Kubernetes workloads, and legacy workloads. Created and maintained by Tigera, Calico Open Source offers a wide range of support for your choice of data plane whether it’s Windows, eBPF, Linux, or VPP. We’re excited to announce our new certification course for Azure, Certified Calico Operator: Azure Expert!

When you’re using an application or tool, it’s very important to make sure things are working as they should. For this reason, health checks are critical. A health check is when an application or tool checks its own components and dependencies, then either publishes or exposes a notification method if there is a problem.

If you are new to Docker, you may find it challenging to understand all the terms. It can seem like everyone has a different idea of what Docker terms mean, and sometimes, terms get used interchangeably. For instance, you — like others who are learning about Docker — may wonder how a Docker image differs from a Docker container. Their contrasts are subtle but significant.

Imagine this: You are an engineer at a startup. You are responsible for keeping all the applications running smoothly and safely in production. At first, you have things under control, but soon enough things start getting more complex.

After these last releases Kubewarden now has support for verifying the integrity and authenticity of artifacts within Kubewarden using the Sigstore project. In this post, we shall focus on verifying container image signatures using the new verify-image-signatures policy. To learn more about how Sigstore works, take a look at our previous post

The new Charmed Operator covering the Capsule Kubernetes extension allows users of Canonical’s Charmed Kubernetes distribution to automatically install and integrate Clastix Capsule Multi-Tenancy as part of the Kubernetes cluster deployment process.

In August 2011, Marc Andreessen wrote an article in The Wall Street Journal entitled “Why Software Is Eating the World.” Andreessen predicted that the leading companies in any industry would be software companies. And indeed, a wave of online software companies arose in which Netflix ate Blockbuster, Apple and Spotify ate Tower Records and the CD, and LinkedIn disrupted the recruiting industry.

Hive smart meters revolutionized the way customers control their energy use. But since their launch in 2012 by UK energy company British Gas, advances in cloud technology and a rapid increase in the number of smart homes has led to an explosion of data.

Continuous integration is a DevOps practice, where developers continuously integrate the code changes into a central repository. It most often refers to the build or the integration stage of the software release process. A continuous integration service helps to automatically build and run unit tests on the new code changes to find any errors instantly.

Continuous integration (CI) is a development practice where development teams can make small, frequent changes to code. With an automated build which verified the code each time developers verify their changes into the version control repository. Which helps the development teams to detect any defect in an early stage. Continuous integration is the first part of CI/CD, which enables the development team to release the code changes gradually to production quickly and regularly.

If you are on Shipa Cloud today, you will have noticed a new module called Insights. We are pleased to announce the initial release of Shipa Insights and certainly have a lot in store as we continue to build out the module. As more items continue to shift left towards the developer and the rise of the full lifecycle developer continues to occur, outside of technical non-functional requirements such as connectivity, reporting and metrics are also important.

To provide world-class developer experiences and get applications to production quickly and securely, you need a team of experts devoted to running your platform as a product. For organizations that build and publish software at scale, developing the tech stack on which developers will create applications and push them to production is often the main focus.

With KubeCon underway, many of us in the cloud native community are looking forward to learning about the newest innovations from the companies we follow. At SUSE, we’ve been working hard to deliver some new enhancements to Rancher with our 2.6.5 version. I want to briefly take you through the highlights of this release and why we’re excited about these new additions.

Like your virtual machine running another virtual machine , today thanks to Loft Labs, you are now able to run multiple virtual Kubernetes clusters in a Kubernetes cluster. The vcluster project is focused on creating fully functional virtual Kubernetes clusters inside a base cluster allowing for a different approach to multitenancy than spinning up a separate Kubernetes cluster. A core use case of Shipa is the ability to have abstractions that make deploying to multiple clusters easy for developers.

A Kubernetes environment includes a wide range of resources—such as clusters, nodes, and pods—that work together to run dynamic applications at scale. In order to monitor a Kubernetes application effectively, you need a multi-dimensional view into your clusters’ health that encompasses the complex dependency relationships among these resources.

Today we’re excited to make three major announcements. First, we’re making it easier to adopt the very popular Codefresh GitOps CD with a fully SaaS offering that is hosted and managed by Codefresh. We’ve heard from many in the community that they’d like to get away from managing Argo CD and focus just on deploying and managing their applications. Hosted GitOps CD makes it easier than ever to adopt GitOps, just create an account, connect your target clusters, and deploy.

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.

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.

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.

Scaling data science is hard. From natural language processing for model-driven policy approvals to image classification in biotechnology to supply chain risk and anomaly detection in advanced manufacturing, data science brings tremendous promise—but not without challenges. Only 21 percent of businesses are gaining a major competitive advantage through the use of data and analytics tools, according to a recent survey.

For those managing enterprise software development organizations, the concept of software supply chains—that is, the set of sources and actions that take software from “raw materials” to a finished product—might represent an abstract concept. While this definition is essentially correct, it doesn’t do enough to explain how supply chains can be complementary to your existing continuous integration and continuous deployment (CI/CD) environments.

In April, we made Civo Academy publicly available for all. This was a pivotal step to put developers first so anyone with an interest can learn everything they need to know to create and maintain their Kubernetes environment. We also released a new report called "The Cost of Cloud", a white paper looking into the complexity of cloud costs for businesses and alternatives beyond the hyperscalers.

Containerization and Kubernetes have taken the DevOps world by storm in the past decade. More and more companies have turned to this technology to enhance their deployment workflows and cut costs. Examples like Pokemon Go and OpenAI would not have been feasible without Kubernetes. While Kubernetes is a growing technology in the current times, it comes with a relatively steep learning curve.

Epinio takes developers from application to URL in one step. In this blog post, I’m going to tell you about the new Epinio extension for Docker Desktop, that allows you to run Epinio on your laptop. DevOps are very interested in the details of containerized workloads and Kubernetes especially, but for developers, the abstraction layer provided by Kubernetes might not be too relevant to their daily work.

Objects are fundamental aspects of Kubernetes (K8s). To work with K8s, you need to understand how basic objects function. In this article, we’ll explain the purposes of the K8s objects you’ll run into most frequently. Objects are separated into two categories: Primitives and Controllers.

You can tell the maturity of something by its challenges. For example, the problems of a 27-year-old are different from those of a 47-year-old. In case it’s not clear, this is my attempt at making a relatable analogy to the maturity of Kubernetes. Though, it might be more accurate to say Kubernetes has reached a point of ubiquity; industry analyst research, foundation surveys, and studies including VMware’s 2022 State of Kubernetes report certainly indicate such.

Over the weekend, I visited one of my favorite grocery stores to pick up one item, my favorite fruit e.g star fruit. Because of the location, the grocery star started to implement parking validation so folks would not abuse their free parking deck for extended periods of time. As I just had a handful of star fruits, I decided to use the self-checkout. This was my first time buying produce via self-checkout.

Leading organizations around the world are adopting cloud-native technologies to build next-generation products because cloud native gives them the agility that they need to stay ahead of their competition. Although cloud native and Kubernetes are very disruptive technologies, there is another technology that is probably the most disruptive technology of our generation, and that is artificial intelligence (AI) and its subset, machine learning (ML).

Picture this… You just got your second cup of coffee and you’re walking back to your desk. The phone in your pocket begins vibrating as a flurry of emails show services are bouncing. The notifications say services were down but are now back up. You hustle back to your desk, spill a little coffee on your notepad, and open the VMware vSphere client to see a host in a disconnected state.

Kubernetes, a Greek word meaning pilot, has found its way into the center stage of modern software engineering. Its in-built observability, monitoring, metrics, and self-healing make it an outstanding toolset out of the box, but its core offering has a glaring problem. The Kubernetes logging challenge is its ephemeral resources disappearing into the ether, and without some 2005-style SSHing into the correct server to find the rolled over log files, you’ll never see the log data again.

For an application developer, there is certainly a long road between an idea/feature and getting deployed into production with Kubernetes. From a development perspective, having a low barrier of entry and the ability to iterate is key. From a platform engineering/DevOps perspective, creating gains in engineering efficiency all while creating and enforcing policies that do not stifle innovation is key.

Prometheus 2.35 was released last month, focusing on a better integration with cloud providers. It also improved the service discovery, performance, and resources usage. One key change was the migration to Go v1.18. It has brought some changes in the support for TLS 1.0, 1.1, and certificates signed with the SHA1 hash function. Welcome to this first edition of What’s new in Prometheus. We love Prometheus, the de-facto open source standard monitoring tool!

Enterprises lately are understanding the need to move their business applications to cloud. Well, one of the major contributing reasons for this move is the rising OpEx and the heavy debt of managing applications in their own environment. Cloud providers are waiting for such opportunities where enterprises are planning to migrate to cloud, the question is will it help or not?

We consistently follow the upstream release cadence to provide our users and customers with the latest improvements and fixes, together with security maintenance and enterprise support for Kubernetes on Ubuntu. This blog is a quick overview of the latest development highlights that are made available in Canonical Kubernetes 1.24 as well as a look at our favourite upstream enhancements.

With recent releases, the Kubewarden stack supports verifying the integrity and authenticity of content using the Sigstore project. In this post, we focus on Kubewarden Policies and how to create a Secure Supply Chain for them.

Things would be much simpler if we based all we built on Kubernetes on a single tenant type of architecture, meaning a single application running on the entire Kubernetes cluster with a single team who could access it. As teams scale Kubernetes adoption within their organizations, they see a different scenario instead, one with multi-tenant deployments performed by multiple teams and, most probably, across multiple clusters.

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.

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).

When I left Red Hat to join SUSE as a Technical Marketing Manager at the end of 2021, I heard about Harvester, a new Hyperconverged Infrastructure (HCI) solution with Kubernetes under the hood. When I started looking at it, I immediately saw use cases where Harvester could really help IT operators and DevOps engineers. There are solutions that offer similar capabilities but there’s nothing else on the market like Harvester.