Quickly launching Kubernetes clusters

kubernetes cloud infrastructure
2026-01-23
By Thalassa Cloud

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.

Latest Posts

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.

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 Node Pool Autoscaling on Thalassa Cloud

We are excited to announce the launch of Node Pool Autoscaling for our Managed Kubernetes service. This feature automatically adds or removes worker nodes in your node pools based on your workloads’ resource demands, ensuring optimal capacity while helping you control costs. Scale Automatically with Demand The Node Pool Autoscaler uses the upstream Kubernetes Cluster Autoscaler to monitor your cluster resource usage and make scaling decisions. Autoscaling is configured per node pool.

Pod Security Standards: Practical Hardening for Kubernetes

Pod Security Standards (PSS) are a low‑friction way to harden clusters by default. With Pod Security Admission (PSA), you can enforce least‑privilege at the namespace level and prevent risky pods from ever being created. It’s simple, auditable, and fits cleanly into GitOps. Improving your security posture Implementing Pod Security Standards is crucial as it helps reduce the blast radius by blocking privilege escalation and host-level access. It allows teams to catch misconfigurations early during the admission phase rather than after deployments, ensuring issues are addressed promptly.

VPC‑Only Access for Kubernetes Clusters

We’ve added support for VPC‑only access to Kubernetes control planes. When enabled, the cluster’s public API endpoint is disabled and the Kubernetes API is reachable only from within your Virtual Private Cloud. This helps teams meet stricter security and compliance requirements without sacrificing operational access. VPC-only access is valuable for DevOps teams because it boosts security by removing the internet-facing API endpoint, which reduces the attack surface. It also makes network rules and identity limits clearer by using your VPC as the boundary.

Kubernetes v1.33.4-0 and v1.32.8-0: Security Fixes and Component Updates

We’re excited to announce the release of two new Kubernetes versions in Thalassa Cloud: v1.33.4-0 and v1.32.8-0. These releases bring security fixes, component updates, and enhanced stability for your Kubernetes workloads. Security Fixes Both releases address a medium security vulnerability: CVE-2025-5187: Nodes can delete themselves by adding an OwnerReference A vulnerability exists in the NodeRestriction admission controller where node users can delete their corresponding node object by patching themselves with an OwnerReference to a cluster-scoped resource.