Kubernetes in Cleura Cloud
Cleura Cloud has two management facilities for Kubernetes clusters:
In most scenarios, Gardener is the preferred option, since it supports more recent Kubernetes versions and offers you a greater degree of “hands-off” management.
For more details on the relative merits of both options, refer to the sections below.
General characteristics
| Gardener | Magnum | |
|---|---|---|
| Kubernetes Cloud Provider | OpenStack | OpenStack |
| Base operating system for nodes | Garden Linux | Fedora CoreOS |
| Latest installable Kubernetes minor release | 1.29 | 1.24 |
API and CLI support
| Gardener | Magnum | |
|---|---|---|
| Manageable via Cleura Cloud REST API | ||
| Manageable via OpenStack REST API | ||
| Manageable via OpenStack CLI |
Updates and upgrades
| Gardener | Magnum | |
|---|---|---|
| Automatic update to new Kubernetes patch release | ||
| Rolling upgrade to new Kubernetes minor release | ||
| Automatic upgrade to new Kubernetes minor release | ||
| Rolling upgrade to new base operating system release | ||
| Automatic upgrade to new base operating system release |
Functional features
| Gardener | Magnum | |
|---|---|---|
| Built-in private registry for container images | ||
| Hibernation | ||
| Manual vertical scaling (bigger/smaller worker nodes) | 1 | |
| Vertical autoscaling | ||
| Manual horizontal scaling (more/fewer worker nodes) | ||
| Horizontal autoscaling | 2 | |
| Kubernetes dashboard | 3 |
Charges and billing
| Gardener | Magnum | |
|---|---|---|
| Monthly subscription fee | ||
| Cleura Cloud charges for Kubernetes control plane nodes | ||
| Cleura Cloud charges for Kubernetes worker nodes |
-
Vertical scaling is only supported via defining additional worker node groups. ↩
-
You must deploy Magnum Cluster Autoscaler to use horizontal autoscaling. ↩