Browser OIDC login for tcloud CLI

cli security
2026-07-07
By Thalassa Cloud
Until now, the default way to authenticate tcloud was a Personal Access Token (PAT): create one in the Console, paste it into tcloud context create, and hope it never ends up in shell history, a dotfile, or a shared screen recording. That works for automation, but it is a poor default for engineers who just want to manage clusters from a laptop. With tcloud v0.20.0, browser-based OIDC login is the default.

Topics

Latest Posts

DBaaS Postgres: An Overview of Our Managed PostgreSQL Service

Last year we introduced Database as a Service (DBaaS) with PostgreSQL. In January 2026 we added the next set of features. Thalassa Cloud’s DBaaS for PostgreSQL gives DevOps teams a fully managed, production-ready Postgres experience—from high availability and automated backups to extensions for analytics and data workloads. Here’s an overview of what the service offers and what’s new. High Availability with Replication Our Database service is built for high availability and uptime.

Kubernetes v1.35 Available on Thalassa Kubernetes Service

We’re announcing two new Kubernetes releases in Thalassa Cloud: v1.35.1-0 and v1.34.3-0. These releases include various patches and upgrades of the container runtime, Kubernetes, Cilium and more. Available Versions v1.35.1-0 release notes. v1.34.3-0 documentation tcloud kubernetes upgrade The tcloud kubernetes versions command lists all available Kubernetes versions in Thalassa Cloud, along with their component versions and release information. Refer to this table to select a version for new deployments or to confirm that runc 1.

Quickly launching Kubernetes clusters

As we continue launching and introducing new cloud services, recently we have been receiving feedback that it can be overwellming to quickly try out our platform. You need familiarity with other cloud platforms such as AWS, Azure to fully understand the services we are offering. This makes sense, as we are building an alternative for the hyperscaler clouds, so we focus on building blocks, APIs and tight service integrations. But as we love to also make things easier to just try out and see what we have, without having to setup a terraform project, or do a lot of clickops work, we are happy to introduce a new feature that allows people to quickly launch a preconfigured environment with a Kubernetes cluster and other Infrastructure.

Nederlandse Cloud zonder Compromissen

2026-01-10
Nederlandse Cloud zonder Compromissen Voor Nederlandse DevOps teams die hun data en digitale operaties volledig onder Europese controle willen houden, is een onafhankelijke Nederlandse cloud provider niet langer een optie—het is een vereiste. Risico’s rond regelgeving en business continuiteit worden steeds belangrijker in het Nederlandse IT-landschap. Steeds meer organisaties kiezen daarom voor een Nederlandse cloud provider als alternatief voor de buitenlandse hyperscalers. Een argument wat je nog wel vaak hoort is dat het Europese aanbod nog beperkt is—DevOps teams die een stap achteruit moeten doen en veel meer diensten volledig zelf inhouse moeten opzetten.

Kubernetes v1.34.2-0 and v1.33.6-0: Security Fixes and Component Updates

We’re announcing two new Kubernetes releases in Thalassa Cloud: v1.34.2-0 and v1.33.6-0. These releases include security fixes that address high-severity vulnerabilities in runc, along with important component updates and stability improvements. Critical Security Fixes Both releases include runc 1.3.3, which fixes three high-severity security vulnerabilities: CVE-2025-31133 CVE-2025-52565 CVE-2025-52881 These vulnerabilities could allow full container breakouts by bypassing runc’s restrictions for writing to arbitrary /proc files. We recommend upgrading your clusters to these versions as soon as possible to mitigate these security risks.

Why Node Pool Autoscaling Matters for Your Infrastructure

Running Kubernetes clusters often means balancing two competing priorities: ensuring your workloads have enough resources to perform well, and not overspending on idle infrastructure. Node Pool Autoscaling solves this by automatically adjusting your node pool size based on actual demand. What it solves Autoscaling directly addresses two key challenges—all related to how efficiently you use your infrastructure resources. 1. The Cost Problem Without autoscaling, you typically size your node pools for peak demand.

Introducing VPC Peering on Thalassa Cloud

We are excited to announce the availability of VPC Peering on Thalassa Cloud. This feature lets you connect Virtual Private Clouds (VPCs) securely though our private network, enabling private network communication between VPCs without using the public internet or Site-to-Sites. It works across organisation accounts. Private Network Connections VPC Peering creates a direct network connection between two VPCs. Traffic between peered VPCs stays on the private network and never touches the public internet, providing secure, low-latency communication between your VPCs.