We are pleased to announce that a new Rancher Desktop version with additional configuration options, deployment profiles, a gvisor-based networking stack on Windows and several other improvements has just been released!

In this post we want to give a simple introduction for using network policies in a sample project and explaining how it works in K3s to help improving the security of your deployments. There is a common misunderstanding about K3s support for network policies, as K3s is using flannel CNI by default, and the Flannel CNI doesn’t support network polices.

Rancher is a Kubernetes management platform that creates a consistent environment for multicloud container operation. It solves several of the challenges around multicloud Kubernetes deployments, such as poor visibility into where workloads are running and the lack of centralized authentication and access control. Multicloud improves resiliency by letting you distribute applications across providers.

Since the very first version, Epinio has made use of an internal S3 endpoint to store the user’s projects in the form of aggregated tarballs. Those objects are then downloaded and staged by the internal engine’s pipeline and, finally, they are deployed into the Kubernetes cluster as consumable applications. Epinio makes use of S3 as an internal private service. In this scenario, S3 can be thought of as an internal ephemeral cache with the purpose of storing temporary objects.

I am thrilled to announce that SUSE has been recognized by G2, the world’s largest and most trusted software marketplace, as one of the Top 25 German Companies in their “Best Software Awards” for 2023. At SUSE, we have always been dedicated to providing our customers with the best possible software solutions and services. This award by G2 is a testament to the hard work and dedication of our entire team.

Companies face multiple challenges when migrating their applications and services to the cloud, and one of them is infrastructure management. The ideal scenario would be that all workloads could be containerized. In that case, the organization could use a Kubernetes-based service, like Amazon Web Services (AWS), Google Cloud or Azure, to deploy and manage applications, services and storage in a cloud native environment. Unfortunately, this scenario isn’t always possible.

Kubernetes has firmly established itself as the leading choice for container orchestration thanks to its robust ecosystem and flexibility, allowing users to scale their workloads easily. However, the complexity of Kubernetes can make it challenging to set up and may pose a significant barrier for organizations looking to adopt cloud native technology and containers as part of their modernization efforts.

We’re pleased to announce the availability of Kubewarden 1.5.0! This release brings the usual amount of small bug fixes, dependency updates, and a major security enhancement. Let’s take a closer look!

Kubernetes turns 9 this year and with its maturity each year, it brings new challenges that drive seismic influence across the rapidly changing cloud native ecosystem. Each year we see new tools created and existing solutions optimized from new lightweight distributions, new features across Kubernetes management platforms, and container security solutions, all adding value to users but simultaneously contributing to the complexity are facing to run Kubernetes successfully.