Speed vs. Safety: Automating Upgrades in a Production Kubernetes Environment

kubernetes cloud
2025-08-01
By Thalassa Cloud

Running Kubernetes in production means constantly updating your clusters. Upgrades are essential for security and new features, but they require careful timing. Move too quickly, and you might break applications. Delay too long, and you’ll fall behind on security patches and API updates. Why Manual Upgrades Don’t Work Manual Kubernetes upgrades are problematic for DevOps teams. They often lead to inconsistent results across environments and rely on a few team members with the necessary expertise.

Latest Posts

2025-08-01

Speed vs. Safety: Automating Upgrades in a Production Kubernetes Environment

Running Kubernetes in production means constantly updating your clusters. Upgrades are essential for security and new features, but they require careful timing. Move too quickly, and you might break applications. Delay too long, and you’ll fall behind on security patches and API updates. Why Manual Upgrades Don’t Work Manual Kubernetes upgrades are problematic for DevOps teams. They often lead to inconsistent results across environments and rely on a few team members with the necessary expertise.

Thalassa Cloud Services Roadmap Status - Q3 2025

Whether you’re deploying critical workloads, scaling internal tools, or building your next product; the infrastructure should be secure, predictable, and automation-friendly. We believe the cloud should feel like an API, not a maze of GUIs or vendor lock-in. That’s why our roadmap is focused on three things: Developer-first IaaS and Kubernetes Security and compliance by design Building blocks for observability and automation Here’s where we are now, and where we’re heading in the third and fourth quarter of 2025.
2025-07-13

Gain More Control with Scheduled Kubernetes Upgrades on Thalassa Cloud

We’ve introduced a new capability to make your cluster operations smoother and more predictable: Scheduled Upgrades for our Managed Kubernetes service.

As a DevOps engineer, you know that staying on supported Kubernetes versions is essential - not just for security patches, but also for ensuring compatibility with the wider CNCF ecosystem. But planning and executing upgrades across environments can be a chore, especially when your running many Kubernetes Clusters.

Introducing the Thalassa Public Cloud

A modern European cloud platform – built from the ground up to put control, automation, and sovereignty back in your hands. At Thalassa Cloud, we believe infrastructure should be modern, flexible, and sovereign – without the complexity or lock-in of hyperscalers. That’s why we’ve launched the Thalassa Public Cloud: a high quality and API first Cloud Services platform designed for DevOps-first teams who want more control and better APIs, without giving up performance or compliance and still want to run their services in Dutch Datacenters.

Introduction into Load Balancers on Thalassa Cloud

Introduction into Load Balancers on Thalassa Cloud Load balancers play a critical role in any cloud infrastructure. They ensure that incoming traffic is reliably routed to healthy services, distributing load across multiple backend targets. On Thalassa Cloud, load balancers are designed from the ground up to be fast, flexible, and API-driven. Built on top of Envoy Proxy, our load balancer implementation provides high performance with a strong focus on automation and self-service.

Why Thalassa Cloud Chose Cilium as the Default CNI

Why We Chose Cilium as the Default CNI for Thalassa Cloud When we set out to build the Kubernetes platform for Thalassa Cloud, we knew that every component we selected had to align with our vision: a platform that prioritizes performance, security, and flexibility. One of the most critical choices we faced was selecting the right Container Network Interface (CNI). Networking is the backbone of any Kubernetes deployment—get it right, and your platform thrives.