Understanding differences between the Kapsule and Kosmos managed Kubernetes services
Scaleway offers two managed Kubernetes solutions: Kapsule and Kosmos. While both serve the purpose of facilitating Kubernetes deployment and management, they cater to different needs and scenarios. Below is a detailed comparison of the two services:
Kubernetes Kapsule
Kapsule is Scaleway's fully managed Kubernetes service, enabling users to deploy, manage, and scale containerized applications seamlessly without the burden of infrastructure management.
- Available in multiple Scaleway regions (PAR, AMS, WAW), allowing users to deploy applications closer to their target audience for enhanced performance.
- Allows users to deploy, manage, and scale containerized applications using Kubernetes without having to manage the underlying infrastructure.
- Automatic scaling, rolling updates, and seamless integration with other Scaleway services like Load Balancers and Object Storage.
- Users can manage their Kubernetes clusters through the Kubernetes API, the intuitive Scaleway console or the Scaleway developer tools (namely Scaleway CLI or the Terraform/OpenTofu provider).
Kapsule is ideal for: Developers and organizations seeking to deploy containerized applications with Kubernetes without the operational overhead of managing Kubernetes infrastructure.
Kubernetes Kosmos
Kosmos is Scaleway's multi-cloud Kubernetes solution, designed to operate across multiple cloud environments, empowering users to deploy applications on different cloud providers, thus offering flexibility and avoiding vendor lock-in.
- Available in multiple Scaleway regions (PAR, AMS, WAW), allowing users to deploy applications closer to their target audience for enhanced performance.
- Offers dedicated control plane options, ensuring dedicated resources for managing Kubernetes clusters.
- Supports various node pool types, including Scaleway instances (x86 and ARM architecture) and external providers, providing users with options to tailor node configurations according to their application needs.
- Uses the Kilo Container Network Interface (CNI) plugin for efficient networking within Kubernetes clusters.
Kosmos is ideal for: Users requiring multi-cloud deployment capabilities, flexibility in node configurations, and extended control over Kubernetes clusters.
Feature comparison
| Kapsule | Kosmos | |
|---|---|---|
| Cloud | Scaleway only | Multi-cloud |
| Regions | PAR, AMS, WAW | PAR, AMS, WAW |
| Node pools | Scaleway Instances only, x86 or ARM | Internal pools: Scaleway Instances, x86 or ARM External pools: Scaleway Elastic Metal, Scaleway RiscV, External providers... |
| Node pools locations | Mono-AZ or Multi-AZ (same region) | Mono-AZ, Multi-AZ, Multi-region, Multi-cloud |
| Container Network Interface plugins | Cilium or Calico | Kilo |
| Auto healing | Yes | Scaleway Instances only |
| Auto scaling | Yes | Scaleway Instances only |
| Container Storage Interface | Yes Persistent volumes (Block Storage) on Scaleway Instances | Scaleway Instances only |
| Free mutualized control plane | Yes | Yes |
| Dedicated control plane options | Yes | Yes |
| Scaleway VPC | Yes Controlled isolation or full isolation | No integration |
| Scaleway Cockpit | Yes | Yes |
| Node pools upgrades | Handled by Kapsule | Internal pools: Handled by Kapsule External pools: Must be carried out manually per node |
AZ = Availability Zone