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.
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.
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.
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.
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.
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.
Deploying private cloud infrastructure is just the beginning for organisations. The real challenge lies in keeping your investment valuable as technology rapidly changes. Thalassa Cloud Haven tackles this issue by offering a private cloud platform designed to adapt and expand alongside your evolving needs, ensuring continuous relevance and value.
Thalassa Cloud Haven is a private cloud platform designed to offer the same cloud services you are used to from the big public clouds, right within your own data centers.
Infrastructure as Code (IaC) is a method that allows teams to implement infrastructure changes in a secure and consistent manner. By using IaC, you can easily maintain and manage your infrastructure just like application code, making it straightforward to implement changes and collaborate across teams.
On Thalassa Cloud, you have two options to achieve this: the official Terraform provider and a community-maintained Pulumi provider. Both solutions enable you to version your infrastructure setup, review changes before applying them, and automate updates across various environments.