Skip to content

Product Blog

Encrypt your Kubernetes Backups using Server Side Encryption

As Kubernetes adoption grows rapidly in enterprises, protecting cluster data is critical. Backups ensure business continuity in case of failures, accidental deletions, or security breaches. For over 2 years, users have depended on the integrated backup/restore capability in the Rafay Platform to dramatically simplify Kubernetes backup and restore operations. When the backups artifacts are stored in public cloud environments, organizations may have a concern with security. One of the most effective ways to secure these backups is by using Server-Side Encryption (SSE). SSE encrypts data at rest within cloud storage services, protecting it from unauthorized access while minimizing operational overhead.

In this blog, I describe the value of SSE encryption for Kubernetes backups and how it enhances security and compliance. I will also describe how administrators can configure and use SSE for backups in the Rafay Platform.

Encryption

Info

Learn about the integrated Backup/Restore capabilities in the Rafay Platform.

Upstream Kubernetes on Flatcar Linux using Rafay

This blog is Part 3 of our series on Flatcar Linux and Kubernetes

  • In Part 1, we introduced Flatcar Linux and why it is a great fit for Kubernetes.
  • In Part 2, we covered how to install a Flatcar instance locally.
  • In this Part 3, we focus on deploying and managing Upstream Kubernetes on Flatcar Linux using Rafay MKS.

Our upcoming February release will introduce a number of new features and enhancements.We will write about these in separate blogs. This blog is focused on support for Upstream Kubernetes based on Rafay MKS on nodes running Flatcar Linux. The Rafay platform enables users to seamlessly provision new clusters and perform in-place upgrades of Kubernetes clusters, simplifying lifecycle management.

For more details on Flatcar Linux, visit the official Flatcar Linux website.

Flatcar Logo


Provision Cluster

Rafay MKS based Upstream Kubernetes clusters can be configured and provisioned on Flatcar Linux using all the supported interfaces i.e.

  • Web Console
  • API
  • CLI (declarative spec)
  • GitOps
  • Rafay Terraform/OpenTofu Provider

In this blog, we will demonstrate this using the web console and the Rafay RCTL CLI.

Flatcar Linux: A Great Fit for Kubernetes

In the fast-evolving landscape of containerized applications and cloud-native technologies, choosing the right operating system for your Kubernetes cluster can sometimes make a very big difference. Enter Flatcar Container Linux, an open-source, minimal, and immutable Linux distribution tailored specifically for running containers.

Flatcar is an excellent choice for Kubernetes and modern cloud-native environments. In Aug 2024, Flatcar Linux was accepted as a CNCF project.

This is a 3-part blog series. In this blog, we'll explore what Flatcar Linux is, why it’s uniquely suited for Kubernetes, and the benefits it brings relative to generic Linux.

Flatcar Logo


What Is Flatcar Linux?

Flatcar Linux is a lightweight and container-optimized Linux distribution designed to provide a secure, consistent, and low-maintenance platform for containerized applications. Originally forked from CoreOS after its deprecation, Flatcar has carried forward the same principles of immutability, simplicity, and reliability, making it a preferred choice for cloud-native deployments.

The most interesting capabilities of Flatcar are:

Immutable Infrastructure

The root file system is read-only and immutable, preventing accidental or malicious changes.

Atomic Updates

Updates are applied atomically, ensuring consistency and eliminating the risk of partial updates.

Container-Native Design

It is optimized for running containers specifically with Kubernetes in mind.

Reduced Attack Surface

The minimalist design reduces the attack surface, and security features like SELinux and secure defaults are enabled out of the box.


Why Flatcar Linux Is a Good Fit for Kubernetes

Kubernetes, as a container orchestration platform, relies on the underlying operating system to provide a stable, efficient, and secure foundation. Here are some reasons why Flatcar Linux is an excellent fit for Kubernetes clusters: s

1.Minimal and Lightweight

Flatcar Linux is stripped down to the essentials required for container workloads. This minimalism reduces complexity and resource consumption, ensuring Kubernetes nodes are efficient and responsive.

2.Immutable

In a Kubernetes cluster, consistency across nodes is crucial. Flatcar’s immutable infrastructure ensures that all nodes run the same configuration, eliminating configuration drift and making it easier to manage large-scale deployments.

3.Automatic and Atomic Updates

Flatcar’s update mechanism is built with atomicity in mind. Updates are applied as a single transaction and can be rolled back if necessary. This is invaluable in a Kubernetes environment where uptime and reliability are critical.

4.Security First

Flatcar provides a minimal attack surface, coupled with features like read-only file systems and SELinux. This ensures that Kubernetes nodes are resilient against vulnerabilities and exploits.

5. Container-Optimized Kernel

Flatcar comes with a kernel optimized for running containers. It integrates seamlessly with Docker, Kubernetes, and other container runtimes, ensuring smooth performance and compatibility.


Conclusion

Flatcar Linux is an excellent operating system for Kubernetes and modern containerized workloads. Its immutable design, security features, and minimal footprint align perfectly with the needs of cloud-native environments. By adopting Flatcar Linux, organizations can achieve greater operational efficiency, enhanced security, and improved reliability for their Kubernetes clusters.

If you’re looking for a secure, reliable, and easy-to-manage operating system for your Kubernetes environment, Flatcar Linux is well worth considering. Its purpose-built nature ensures that your infrastructure is optimized for the demands of modern, containerized workloads. Visit flatcar.org to learn more and get started!

In the 2nd blog, we will demonstrate how you can configure, install and operate Flatcar Linux. In the 3rd and final blog in the series, we will describe how you can provision and operate Rafay MKS Kubernetes Clusters on Flatcar Linux based nodes. Support for Flatcar Linux with Rafay MKS is coming in a few weeks.

Kubernetes v1.32 for Rafay MKS

As part of our January release, alongside other enhancements and features, we are adding support for Kubernetes v1.32 with Rafay MKS (i.e., upstream Kubernetes for bare metal and VM-based environments).

Both new cluster provisioning and in-place upgrades of existing clusters are supported. As with most Kubernetes releases, v1.32 deprecates and removes several features. To ensure zero impact to our customers, we have validated every feature of the Rafay Kubernetes Operations Platform on this Kubernetes version.

Kubernetes v1.32 Release

Get Started with Auto Mode for Amazon EKS with Rafay

This is Part 3 in our series on Amazon EKS Auto Mode. In the previous posts, we explored:

  1. Part 1: An Introduction: Learn the core concepts and benefits of EKS Auto Mode.
  2. Part 2: Considerations: Understand the key considerations before Configuring EKS Auto Mode.

In this post, we will dive into the steps required to build and manage an Amazon EKS cluster with Auto Mode template using the Rafay Platform. This exercise is specifically well suited for platform teams interested in providing their end users with a controlled self-service experience with centralized governance.

EKS Auto Mode Cluster in Rafay

EKS Auto Mode - Considerations

In the introductory blog on Auto Mode for Amazon EKS, we described the basics of this new capability that was announced at AWS re:Invent 2024. In this blog, we will review considerations that organizations need to factor in before using EKS in Auto Mode.

Note

Please consider this as a living/evolving document. EKS Auto Mode is relatively new and we update this blog with new learnings/findings.

Considerations for EKS Auto Mode

EKS Auto Mode - An Introduction

The Rafay team just got back late last week from an incredibly busy AWS re:Invent 2024. Congratulations to the EKS Product team led by our friend, Nate Taber for the launch of Auto Mode for EKS.

Since this announcement last week, we have had several customers reach out and ask us for our thoughts on this newly launched EKS Auto Mode service. There are several blogs that already describe "How Auto Mode for EKS works etc". In this blog series, I will attempt to provide perspective on "Why", "Why Now?" and "What this means for the industry".

EKS Auto Mode

Deploying Custom CNI (Kube-OVN) in Rafay MKS Upstream Kubernetes Cluster Using the Blueprint Add-On Approach

In continuation of our Part 1 intro blog on the Kube-OVN CNI, this is Part 2, where we will cover how easy it is to manage CNI configurations using Rafay's Blueprint Add-On approach.In the evolving cloud-native landscape, networking requirements are becoming more complex, with platform teams needing enhanced control and customization over their Kubernetes clusters. Rafay's support for custom, compatible CNIs allows organizations to select and deploy advanced networking solutions tailored to their needs. While there are several options available, this blog will focus specifically on deploying the Kube-OVN CNI. Using Rafay’s Blueprint Add-On approach, we will guide you through the steps to seamlessly integrate Kube-OVN into an upstream Kubernetes cluster managed by Rafay’s Managed Kubernetes Service.

Our upcoming release, scheduled for December in the production environment, introduces several new features and enhancements. Each of these will be covered in separate blog posts. This particular blog focuses on the support and process for deploying Kube-OVN as the primary CNI on an upstream Kubernetes cluster.

kube ovn

Watch a video showcasing how users can customize and configure Kube-OVN as the primary CNI on Rafay MKS Kubernetes clusters.

The Kube-OVN CNI: A Powerful Networking Solution for Kubernetes

Kubernetes has become the de facto standard for orchestrating containerized applications, but efficient networking remains one of the biggest challenges. For Kubernetes networking, Container Network Interface (CNI) plugins handle the essential task of managing the network configuration between pods, nodes, and external systems. Among these CNI plugins, Kube-OVN stands out as a feature-rich and enterprise-ready solution, designed for cloud-native applications requiring robust networking features.

In this blog, we will discuss how it is different from popular CNI plugins such as Calico and Cilium and use cases where it is particularly useful.

Kube-OVN Logo

Introducing "Schedules" on the Rafay Platform: Simplifying Cost Optimization and Compliance for Platform Teams

Platform teams today are increasingly tasked with balancing cost efficiency, compliance, and operational agility across complex cloud environments. Actions such as cost-optimization measures and compliance-related tasks are critical, yet executing these tasks consistently and effectively can be challenging.

With the recent introduction of the “Schedules” capability on the Rafay Platform, platform teams can now orchestrate one-time or recurring actions across environments in a standardized, centralized manner. This new feature enables teams to implement cost-saving policies, manage compliance actions, and ensure operational efficiency—all from a single interface. Here’s a closer look at how this feature can streamline your workflows and add value to your platform operations.

Schedules