Provider: Chasm Technologies
Over the last decade, enterprise infrastructure teams have been migrating workloads to Kubernetes. Applications, APIs, batch jobs, and data pipelines—all these elements thrive within a containerized environment. The operational advantages are well-documented, encompassing declarative configurations, horizontal scaling, self-healing capabilities, seamless CI/CD pipeline integration, and enhanced observability. Kubernetes has certainly emerged as the go-to operating model for production workloads.
However, desktop solutions remain outside the Kubernetes framework.
Secure desktop and application delivery crucial for remote work and industries with strict regulations remain outside the Kubernetes paradigm. Traditional Virtual Desktop Infrastructures (VDI) were developed under different assumptions, involving pre-allocated VM pools, custom management planes, and proprietary appliances—hence resulting in a fragmented infrastructure landscape. This bifurcation separates a modern cloud-native application layer from a manually managed desktop layer, leading to inefficiencies.
This disjointedness incurs costs—different toolsets, unique scaling behaviors, and varied observability approaches complicate operational workflows. Even engineers adept in Kubernetes find themselves switching contexts when addressing desktop infrastructure issues.
Importantly, this division is unnecessary. Kubernetes is inherently suited for delivering secure containerized workspaces. A session is simply a container; scaling occurs as per demand; and configuration settings should be declarative. The missing link was a platform designed to seamlessly integrate these functionalities.
Why Now?
As organizations advance their investments in container solutions, the call for Kubernetes-native workspace delivery has surged. After years of standardizing Helm, GitOps workflows, and Kubernetes-native observability, platform teams are reluctant to compromise when it comes to desktop infrastructure. The fundamental question has shifted from “Can I run this on Kubernetes?” to “Why isn’t this already running on Kubernetes?”
Simultaneously, the urgency surrounding security for containerized workspace delivery has escalated. Browser-based containerized workspaces offer session isolation that traditional VM-based desktops cannot match. Each session is temporary and securely contained, facilitating better security for organizations handling sensitive data, insider risks, or third-party access scenarios.
The convergence of Kubernetes-native infrastructure expectations with robust containerized session security creates a timely opportunity for innovative platforms to provide both simultaneously.
What Does a Kubernetes-Native Deployment Entail?
A Kubernetes-native deployment utilizes Kubernetes as the control plane for workspace infrastructure. This means managing orchestration, scaling, and lifecycle with the same declarative model used throughout the platform. Instead of relying on dedicated management appliances or pre-provisioned desktop pools, the entire infrastructure operates within existing CI/CD, GitOps, observability, and security workflows, ensuring a consistent operational model without the need for disparate toolsets.
Kasm Workspaces, a browser-based workspace platform, is purpose-built to leverage Kubernetes for efficient orchestration and delivery. It is designed for real-world enterprise environments, featuring production-grade Helm charts aligned with Kubernetes conventions, reliable upgrade paths, and a validated backend architecture tested across numerous deployments. Additionally, RDP gateway components are specifically designed for Kubernetes architectures, allowing seamless access to Windows and Linux virtual machines through a unified platform.
Main Features:
-
Horizontal session scaling orchestrated by Kubernetes based on actual demand—no need for pre-warmed VM pools.
-
Declarative configurations with Helm values to facilitate GitOps and CI/CD integration for workspace infrastructure.
-
Namespace-level isolation that complies with existing RBAC policies, ingress controllers, and secret management.
-
Export metrics for full integration with Prometheus and pre-existing observability stacks.
-
Rolling builds are standard, reducing maintenance windows and enhancing version control predictability.
Real-World Applications
Regulated Industry Remote Access: Financial services organizations utilizing Kubernetes-based application platforms can deploy Kasm on the same cluster, managing isolated browser and application sessions for analysts and advisors through a unified GitOps pipeline.
Contractor and Third-Party Access: Organizations onboarding contractors or external vendors needing privileged access can utilize Kasm sessions on Kubernetes, dynamically scaling resources during engagements while maintaining no permanent access points, thus ensuring containerized isolation across all session boundaries.
AI/ML Development Environments: Teams developing AI models require secure, GPU-enabled development environments rarely offered by generic cloud desktops. Deploying Kasm with NVIDIA MiG multi-instance GPU support on Kubernetes allows platform teams to provision partitioned GPU resources for isolated workspace sessions, granting data scientists the computational power they need without compromising shared infrastructure security.
Operational Shift
The practical outcome of a Kubernetes-native workspace platform is that platform teams no longer have to treat workspace infrastructure as a distinct category. Workspace platforms can be handled by the same engineers responsible for application deployments. Configurations can be managed in the same pipelines governing application settings, and the overall health of workspaces can be monitored within the same dashboards used for application health checks.
This consolidation reduces overhead, enhances consistency, and removes context-switching challenges that have made desktop infrastructure a persistent headache for cloud-native organizations.
For companies still relying on legacy VDI alongside modern cloud infrastructure, the question has shifted from whether a Kubernetes-native option exists to when they should implement the transition.
To explore Kubernetes-native workspace delivery firsthand, visit kasm.com or try the Community Edition for yourself.
Daniel Ben-Chitrit is the forthcoming Chief Product Officer at Chasm Technologies.
Sponsored articles are created by companies paying us for placement or through a business relationship with VentureBeat and are always clearly identified. For additional information, please reach out to us at [email protected].
Source: venturebeat.com