VPC‑Only Access for Kubernetes Clusters

kubernetes security
2025-09-20
By Thalassa Cloud

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.

Latest Posts

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.

VPC Networking Upgrade with Custom Route Tables

Introducing Custom Route Tables for VPCs Networking is at the core of any cloud infrastructure, and Thalassa Cloud’s Virtual Private Clouds (VPCs) provide secure, isolated environments for deploying workloads. Until now, our VPC networking was fully automated—when a NAT Gateway or other networking component was created, routing rules were automatically assigned. While this made deployment seamless, it limited flexibility for advanced networking use cases. With the introduction of custom route tables, users now have full control over how traffic moves within their VPCs, enabling: