Kubernetes Service
CloudFerro Kubernetes as a Service offers a container orchestration solution smoothly integrated with our European public cloud. Built on OpenStack and designed cloud-native from the ground up, the Service helps you run production-grade Kubernetes clusters with integrated cloud storage and networking. Kubernetes enables fast deployment of highly scalable applications, systems, and workloads, reducing both infrastructure and development overhead. Data scientists can also use Kubernetes on CloudFerro clouds to run complex workflows, with integrated access to EO data.
Whether you’re deploying microservices, data platforms, or batch workloads, CloudFerro Kubernetes Service helps you get from “idea” to production-grade application deployments faster.
Why teams benefit from a Kubernetes Service?
Kubernetes unlocks speed and portability, but self-managing clusters can quickly become a time sink.
Provisioning
Provisioning takes too long when clusters depend on manual setup and templates are hard to maintain.
Control plane
Operational risk grows when one wrong change can destabilize the control plane or break upgrades.
Scaling
Capacity falls short without a robust, scalable solution.
Integrations
Cloud integration is harder than it looks (load balancers, persistent volumes, networking, GPU).
From OpenStack Magnum to Managed Kubernetes
CloudFerro currently provides two alternatives for running Kubernetes Service clusters: Managed Kubernetes (recommended) and OpenStack Magnum (legacy option).
Managed Kubernetes (recommended)
- Dedicated Managed Kubernetes interfaces (GUI, CLI, IaC)
- CloudFerro operates and monitors the control plane to reduce operational risk
- Designed to prevent unsafe cluster changes by reconciling to the desired state
- Built with enterprise applications in mind, where no downtime throughout cluster’s lifecycle is priority
- New projects, migration of existing applications
Magnum (legacy)
- OpenStack interfaces (GUI, CLI, IaC)
- More responsibility remains on the user side; you control the underlying VMs that run the cluster
- Higher chance that a problematic change or VM issue affects the cluster
- Sufficient and mostly tailored for workflow-based operations (e.g. data processing)
- Existing applications, running on Magnum; specific scenarios of use
For new deployments, we recommend Managed Kubernetes. If you run clusters on Magnum today, you can continue operating them while planning a transition path.
Availability: Poland (Warsaw) and Germany (Frankfurt) Cloud locations.
Cloud-native features, built into the service
CloudFerro Cloud integrations
Native integration with CloudFerro networking and storage: the ability to use LoadBalancer-type services with public IP addresses exposed; shared storage classes available for use from within Kubernetes (PVC).
Autohealing (node recovery)
When a cluster node becomes unhealthy, the auto-healer automatically replaces it with a new server to restore capacity and keep workflows running.
GPU-enabled node pools
Node pools with GPU flavors, pre-configured and integrated to deliver GPU acceleration.
Autoscaling
Autoscaling and node-level healing to keep capacity aligned with demand and reduce manual intervention.
Verified on demanding Earth Observation applications.
Scientific teams use the Kubernetes Service to process large volumes of satellite data that require intensive, scalable use of cloud resources. As part of the solution, we provide documentation with examples of how to integrate Kubernetes with tools relevant to scientific and EO (Earth Observation) workflows.
Pricing that matches how you use Kubernetes
- You pay for compute, storage and networking resources used to run your cluster.
- There’s no additional charge for setting up and running the Kubernetes service.
- EO data access remains available at no extra cost (where applicable).
FAQs
Managed Kubernetes is the recommended path for new clusters, with CloudFerro operating the Control Plane and providing a safer lifecycle experience. Magnum is the legacy option for teams already using OpenStack Magnum workflows.
Yes, Kubernetes clusters integrate with load balancers, floating IPs/ingress, and persistent volumes via storage classes.
You pay for the underlying infrastructure (compute, storage, networking) used by your cluster. There’s no additional Kubernetes service fee.
